action #41207
open[qe-core][functional][ipmi] test fails in reboot_gnome - seems we call some code which we are not allowed to do, need to "reset_consoles" or something? nearly there to a complete run again :)
0%
Description
Observation¶
Installation on an IPMI machine doesn't work for SLE15+.
Reproducible¶
Fails since SLE15.
Expected result¶
The test never worked for SLE15
Suggestions¶
- Create a separate test suite for only text editors that runs after create_hdd_gnome (For text editors that should_be installed on sles, in this case, just vim for now)
- Remove text editor tests from default scenarios (vim in this particular case)
- Schedule reboot test module at the end of the scenario
Acceptance criteria¶
- AC1: Test suite default is able to complete installation and post installation test modules for SLE12-SP5+ and SLE15-SP1+ over IPMI
- AC2: Test suite gnome is able to complete installation and post installation test modules for SLE12-SP5+ and SLE15-SP1+ over IPMI
- AC3: test module vim runs on it's own separate test suite
- AC4: Changes are documented in this ticket.
Further details¶
Always latest result in this scenario:
- latest SLE15-SP2 default(server role) (Coming soon)
- latest SLE15-SP2 gnome (Coming soon)
- latest SLE15-SP1 default (server role)
- latest SLE15-SP1 gnome
- latest SLE15
- former latest, Leanos-DVD
- latest SLE12-SP4
Updated by szarate over 5 years ago
Still happening, connection to gonzo seems to timeout according to the logs of this test)DIE Error connecting to host : IO::Socket::INET: connect: Connection timed out
Updated by szarate over 5 years ago
perhaps disconnect from it (the console), and wait until ssh comes back after 1 minute or a bit more?
Updated by okurz over 5 years ago
except for the "waste time by just blindly waiting"-part, yes :)
Updated by okurz over 5 years ago
shouldn't there be other tickets about ipmi and that we were never complete? Need to reference
Updated by okurz over 5 years ago
- Blocked by coordination #23650: [sle][functional][ipmi][epic][u] Fix test suite gnome to work on ipmi 12-SP3 and 15 (WAS: test fails in boot_from_pxe - connection refused trying to ipmi host over ssh?) added
Updated by okurz over 5 years ago
- Status changed from New to Blocked
- Assignee set to okurz
- Target version changed from Milestone 20 to Milestone 25+
Updated by SLindoMansilla almost 5 years ago
- Description updated (diff)
This ticket should follow #23650
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 25+ to Milestone 25
moving to M25 then
Updated by okurz almost 5 years ago
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 25 to Milestone 26
Updated by mgriessmeier over 4 years ago
- Status changed from Blocked to New
- Assignee deleted (
mgriessmeier) - Target version changed from Milestone 26 to Milestone 28
check with 15SP2
Updated by SLindoMansilla over 4 years ago
- Blocked by action #38423: [sle][functional][u][hard] Refactor first_boot to unify duplicated behavior for remote backend added
Updated by mgriessmeier over 4 years ago
- Target version changed from Milestone 28 to Milestone 32
Updated by tjyrinki_suse over 3 years ago
- Subject changed from [functional][u][ipmi] test fails in reboot_gnome - seems we call some code which we are not allowed to do, need to "reset_consoles" or something? nearly there to a complete run again :) to [qe-core][functional][ipmi] test fails in reboot_gnome - seems we call some code which we are not allowed to do, need to "reset_consoles" or something? nearly there to a complete run again :)
Updated by okurz over 3 years ago
- Status changed from Blocked to Workable
was blocked by #38423 which is "Resolved" by now
Updated by szarate about 3 years ago
Are we seriously testing vim in every scenario? https://openqa.suse.de/tests/5443832#step/vim/6
Updated by okurz about 3 years ago
Well, it's fast and easy and a simple check of a real application. Don't just see it as a test for "just vim" but "just any console application, with colors! :)"
Updated by szarate about 3 years ago
okurz wrote:
Well, it's fast and easy and a simple check of a real application. Don't just see it as a test for "just vim" but "just any console application, with colors! :)"
it's just a test for vim. If I want to check for color support, https://openqa.suse.de/tests/5476680#step/aplay/15 is a better candidate.
Updated by maritawerner almost 3 years ago
So what is the plan here? Fix it or leave it as is? Or skip it?
Updated by livdywan over 1 year ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin about 1 month ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.