action #27108
closed
[sle][functional][ipmi][hard] test fails in qa_net_boot_from_hdd - No SOL updates anymore after installation
Added by nicksinger almost 7 years ago.
Updated over 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-x86_64-textmode@64bit-ipmi fails in
qa_net_boot_from_hdd.
Assumption: The black screen you can see there is the XVnc screen on the worker which normally has a SOL connection opened to the SUT to see/enter commands. For some reason the worker is still connected to the SOL interface (otherwise the backend would try a reconnect and fail after 10 attempts <- not visible in the logs) but there is no output from the SUT on it.
Further investigation why this happens is needed. Maybe the fix is as easy as just reconnecting to the SUT right after the system finished installation.
Acceptance criteria¶
- AC: The module qa_net_boot_from_hdd passes or fail/soft-fail on a proper product bug.
Hypotheses¶
- H1: ipmi machine not working after installation.
- H2: The problem begins on qa_net_boot_from_hdd::prepare_system_shutdown.
- H3: The problem begins on qa_net_boot_from_hdd::assert_shutdown_and_restore_system.
- H4: The sol console was not selected after the installation.
Tasks¶
- E1-1: Restart the job and try to manually connect to the ipmi machine while the job is stuck on module qa_net_boot_from_hdd.
- R1-1: I have verified that when the module qa_net_boot_from_hdd is stuck I can access the ipmi machine and the system was properly installed and working.
- E4-1 Explicitly select sol console after installation.
Reproducible¶
Happens since the boot_from_pxe module was fixed and the test could continue.
Expected result¶
OpenQA can continue testing after the installation of SLE on the SUT
Further details¶
Always latest result in this scenario: latest
- Related to action #26948: [sle][functional][ipmi][hard] Adjust boot_from_pxe to sanely handle multiple network interfaces added
- Subject changed from [sle][functional][ipmi] test fails in qa_net_boot_from_hdd - No SOL updates anymore after intallation to [sle][functional][ipmi] test fails in qa_net_boot_from_hdd - No SOL updates anymore after installation
- Due date set to 2017-11-22
- Target version set to Milestone 12
- Blocks coordination #25510: [sle][functional][u][hard][epic] New test scenario textmode@ipmi added
- Subject changed from [sle][functional][ipmi] test fails in qa_net_boot_from_hdd - No SOL updates anymore after installation to [sle][functional][ipmi][hard] test fails in qa_net_boot_from_hdd - No SOL updates anymore after installation
- Due date changed from 2017-11-22 to 2017-12-20
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: textmode@64bit-ipmi
https://openqa.suse.de/tests/1288917
- Due date changed from 2017-12-20 to 2018-01-30
- Target version changed from Milestone 12 to Milestone 13
unable to commit on that in this year
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: gnome@64bit-ipmi
https://openqa.suse.de/tests/1396376
- Assignee set to SLindoMansilla
- Description updated (diff)
- Status changed from New to In Progress
- Description updated (diff)
R1-1¶
I have verified that when the module qa_net_boot_from_hdd is stuck I can access the ipmi machine and the system was properly installed and working.
- Description updated (diff)
- Has duplicate action #30709: [sle][functional][sle12 sp4] qa_net_boot_from_hdd doesn't start added
- Status changed from In Progress to Workable
At the moment the ipmi machines are defect. nsinger will update the firmware.
Hypothese, the scenario for ipmi was not adapted after disable_grub_timeout
- Status changed from Workable to In Progress
- Description updated (diff)
E4-1 Explicitly select sol console after installation.
R4-1 It works
PR merged: gh#4279
Waiting for verification run on OSD
- Description updated (diff)
- Status changed from In Progress to Resolved
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: gnome@64bit-ipmi
https://openqa.suse.de/tests/1411813
Also available in: Atom
PDF