QA » openQA Project » openQA Tests

After several reruns, the following create_* jobs seem to permanently (today) fail currently:

create_hdd_textmode_intel_ipmi@64bit-ipmi - - -

create_hdd_textmode_intel_ipmi_fips_ker@64bit-ipmi

Those cancel the following:
fips_env_mode_tests_crypt_core_intel_ipmi@64bit-ipmi
fips_env_mode_tests_crypt_tool_intel_ipmi@64bit-ipmi
fips_env_mode_tests_crypt_web_intel_ipmi@64bit-ipmi
fips_ker_mode_tests_crypt_core_intel_ipmi@64bit-ipmi
fips_ker_mode_tests_crypt_kernel_intel_ipmi@64bit-ipmi
fips_ker_mode_tests_crypt_tool_intel_ipmi@64bit-ipmi
fips_ker_mode_tests_crypt_web_intel_ipmi@64bit-ipmi

These however are now passing:
fips_ker_mode_tests_crypt_install_intel_ipmi@64bit-ipmi
(which creates its own HDD)

--edit, ignore the below line, all create their hdds--
Not sure why those two HDD creations always fail although use same WORKER_CLASS and MACHINE, maybe it's just the lack of good timing, whenever that IPMI is working.

Create_hdd now running past IPMI connection and past boot_from_pxe! https://openqa.suse.de/tests/10953255#live

Needed a lot of tries though to get to this point.

But:
This ticket is about boot_to_desktop first of all. Secondly, tests like https://openqa.suse.de/tests/10911858 (fips_ker_mode_tests_crypt_core_intel_ipmi@64bit-ipmi) actually use ISO, not HDD, so why restarting eg create_hdd_textmode_intel_ipmi@64bit-ipmi restarts also these jobs even if the HDD is not even used?

Are there wrong dependencies, and thus hard to get good results as failing tests refuse to be started without restarting create_hdd_*? Maybe "skip parents" could be used to restart instead.

Ok "skip parents" gets one at least (eventually) to "boot_to_desktop" problem again: https://openqa.suse.de/tests/10953868#

So, with problems earlier than this ticket, if create_hdd_* succeeds, one can open the failing at bootloader_start run (documented eg in qe-yam's ticket #126143), and click restart wih "Skip parents" in order to eventually get to this particular ticket, ie boot_to_desktop problem on ipmi.

Comment #2 here can be ignored as I didn't realize yet there is a dependency definition problem of some sort. As an answer to why fips_ker_mode_tests_crypt_install_intel_ipmi@64bit-ipmi is passing - it does not include module boot_to_desktop at all.

This ticket might be about another scheduling issue. When one of the tests succeeded to run at https://openqa.suse.de/tests/10687297, the boot_to_desktop succeeded yes, but there was no bootloader_start to begin with. So, the answer could be to remove bootloader_start?

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: fips_ker_mode_tests_crypt_kernel_intel_ipmi@64bit-ipmi
https://openqa.suse.de/tests/14702279#step/boot_to_desktop/1

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.