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 :)
Added by okurz over 5 years ago.
Updated about 2 months ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 32
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:
- Priority changed from Normal to High
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
perhaps disconnect from it (the console), and wait until ssh comes back after 1 minute or a bit more?
except for the "waste time by just blindly waiting"-part, yes :)
shouldn't there be other tickets about ipmi and that we were never complete? Need to reference
- 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
- Status changed from New to Blocked
- Assignee set to okurz
- Target version changed from Milestone 20 to Milestone 25+
- Description updated (diff)
This ticket should follow #23650
- Description updated (diff)
- Target version changed from Milestone 25+ to Milestone 25
- 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.
- Target version changed from Milestone 25 to Milestone 26
- Status changed from Blocked to New
- Assignee deleted (
mgriessmeier)
- Target version changed from Milestone 26 to Milestone 28
- Blocked by action #38423: [sle][functional][u][hard] Refactor first_boot to unify duplicated behavior for remote backend added
- Status changed from New to Blocked
- Target version changed from Milestone 28 to Milestone 32
- 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 :)
- Status changed from Blocked to Workable
was blocked by #38423 which is "Resolved" by now
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! :)"
- Description updated (diff)
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.
So what is the plan here? Fix it or leave it as is? Or skip it?
- Priority changed from High to Normal
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.
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.
Also available in: Atom
PDF