Actions
action #176541
closed[qe-core]Test module grub_set_bootargs damages Grub on svirt backend
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2025-02-04
Due date:
% Done:
0%
Estimated time:
Difficulty:
easy
Tags:
Description
Observation¶
The create_hhd_gnome_libyui test fails in boot_to_dektop.
This test uses the HDD image provided by create_hdd_gnome@svirt-xen-hvm. Inside this module the reboot works perfectly, but after reboot the grub_set_bootargs module is exectued. And I'm afraid that the modifications done here lead to that error above.
Proof of concept¶
I cloned both test, excluding the module in question with this command:
openqa-clone-custom-git-refspec -c "--parental-inheritance --within-instance" https://github.com/rakoenig/os-autoinst-distri-opensuse/tree/master https://openqa.suse.de/tests/16648166 EXCLUDE_MODULES="yast2_lan,yast2_lan_device_settings,yast2_snapper,yast2_i,yast2_bootloader,yast2_nfs_server,yast2_lan_restart,grub_set_bootargs"
Then the test passes without any problems in boot_to_desktop.
Suggestion¶
Exclude the grub_set_bootargs module for the svirt backend.
Updated by rfan1 2 months ago
- Tags set to bugbusters
- Subject changed from Test module grub_set_bootargs damages Grub on svirt backend to [qe-core]Test module grub_set_bootargs damages Grub on svirt backend
- Status changed from New to In Progress
- Assignee set to rfan1
- Target version set to QE-Core: Ready
Updated by rfan1 2 months ago
- Status changed from In Progress to Feedback
The issue is gone when I tried to re-run the failed jobs.
I noticed some update from xen server:
2025-02-04 03:21:08|command|root@openqaw5-xen|'zypper' '-n' '--no-refresh' '--non-interactive-include-reboot-patches' 'dup' '--replacefiles' '--auto-agree-with-licenses' '--download-in-advance'|
2025-02-04 03:21:11|install|liborc-0_4-0|0.4.28-150000.3.9.1|x86_64||repo-sle-update|a0813478a63346b2eb1f101ad9b73ede8dcb22269ab4ef9a9234617440f6915a|
2025-02-04 03:21:15|install|yast2-iscsi-client|4.6.6-150600.3.14.2|noarch||repo-sle-update|583bff106e80dafe3e8078d4758f26be3d31040da065f4daa60ae776d1bd72c6|
2025-02-04 03:21:15|patch |openSUSE-SLE-15.6-2025-331|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2025-02-04 03:21:15|patch |openSUSE-SLE-15.6-2025-344|1|noarch|repo-sle-update|important|security|needed|applied|
2025-02-05 03:21:00|command|root@openqaw5-xen|'zypper' '-n' '--no-refresh' '--non-interactive-include-reboot-patches' 'dup' '--replacefiles' '--auto-agree-with-licenses' '--download-in-advance'|
2025-02-05 03:21:02|install|libxml2-2|2.10.3-150500.5.20.1|x86_64||repo-sle-update|09b0e4f7589768ad7680dede25ec413beca4b416c4a1bc7d4c0ebe914a351a57|
2025-02-05 03:21:02|install|python3-libxml2|2.10.3-150500.5.20.1|x86_64||repo-sle-update|7d80c7dfa3f47d59b5f37fc029008ada9830f642fd32e2e4767667146503b430|
2025-02-05 03:21:03|install|libxml2-tools|2.10.3-150500.5.20.1|x86_64||repo-sle-update|11231dde67e6158728f785d33af97f5e487bcdfbd45159e989b2701d0355bc94|
2025-02-05 03:21:04|install|bind-utils|9.18.33-150600.3.6.1|x86_64||repo-sle-update|50560140ad510a973b45c301a42d368e10f8234b16a0d23e58f34385c928d185|
2025-02-05 03:21:04|patch |openSUSE-SLE-15.6-2025-348|1|noarch|repo-sle-update|important|security|needed|applied|
2025-02-05 03:21:04|patch |openSUSE-SLE-15.6-2025-355|1|noarch|repo-sle-update|important|security|needed|applied|
2025-02-06 03:21:05|command|root@openqaw5-xen|'zypper' '-n' '--no-refresh' '--non-interactive-include-reboot-patches' 'dup' '--replacefiles' '--auto-agree-with-licenses' '--download-in-advance'|
2025-02-06 03:21:07|install|cpp7|7.5.0+r278197-150000.4.44.1|x86_64||repo-sle-update|e08dd257e9e840ca10c0f8427364a50b6062b6cb7a6e6e9d216d21097439bf2c|
2025-02-06 03:21:09|install|libcurl4|8.6.0-150600.4.21.1|x86_64||repo-sle-update|98d0d4dd18dda10e140fea496543ffa07904dd66be73fd9bdb1bb455b7d9b6cb|
2025-02-06 03:21:10|install|libgfortran4|7.5.0+r278197-150000.4.44.1|x86_64||repo-sle-update|c2f2bb1a6c4a59c51198febeb4bee7d92f5a31fdd2a5055869863915df6812df|
# 2025-02-06 03:21:11 permissions-20240826-150600.10.15.2.x86_64.rpm installed ok
# Additional rpm output:
# Updating /etc/sysconfig/security ...
#
2025-02-06 03:21:11|install|permissions|20240826-150600.10.15.2|x86_64||repo-sle-update|8a9f3a01cb2d061ba9f13beb760fb2188fabda50c6a6c16d4e462a2265ebab6f|
2025-02-06 03:21:11|install|zypper-log|1.14.81-150600.10.22.1|noarch||repo-sle-update|d49e12212fe4f48a247c296e39d991f40165252bb2f7575a6bb89fd6ec20bed6|
2025-02-06 03:21:13|install|libzypp|17.35.19-150600.3.44.1|x86_64||repo-sle-update|b03b64a618c90f8060f8aee52409b80ded76c90e7ab6ac5096e3b2e0dafbc126|
2025-02-06 03:21:14|install|curl|8.6.0-150600.4.21.1|x86_64||repo-sle-update|f221e889e59e3cea1b8e6b7237b3358af99066049826311ab311ecddd0480b80|
# 2025-02-06 03:21:15 zypper-1.14.81-150600.10.22.1.x86_64.rpm installed ok
# Additional rpm output:
# warning: /etc/zypp/zypper.conf created as /etc/zypp/zypper.conf.rpmnew
#
2025-02-06 03:21:15|install|zypper|1.14.81-150600.10.22.1|x86_64||repo-sle-update|48513a7207b173b4cf4f9ed80ad421993cd2c170046c1daa201555f3a030cdb8|
2025-02-06 03:21:16|install|zypper-needs-restarting|1.14.81-150600.10.22.1|noarch||repo-sle-update|f9825c67bcfacfa2e93ac8b39a038f2ca44e7dfc02a0cc0f8e798c7084287173|
2025-02-06 03:21:16|patch |openSUSE-SLE-15.6-2025-358|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2025-02-06 03:21:16|patch |openSUSE-SLE-15.6-2025-363|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2025-02-06 03:21:16|patch |openSUSE-SLE-15.6-2025-367|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2025-02-06 03:21:16|patch |openSUSE-SLE-15.6-2025-369|1|noarch|repo-sle-update|moderate|security|needed|applied|
So let me mark it as feedback, and check if the issue can be seen in next build.
Updated by openqa_review about 1 month ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/16990849#step/boot_to_desktop/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by rfan1 about 1 month ago
- Status changed from Feedback to Resolved
Re-run the parent job could be a workaround
Actions