action #156907
closed[tools][qe-core][leap15.6 Beta]test fails in openqa_bootstrap with Beta build size:M
0%
Description
Description¶
/usr/share/openqa/script/openqa-bootstrap command seems add non existing repo with Beta build.
I didn't check the detail script yet, but seems it has something to do with output of uname -r or uname -m command.
I can see below messages in login console:
Welcome to openSUSE Leap 15.6 Beta - Kernel 6.4.0-150600.9-default (hvc0).
https://openqa.opensuse.org/tests/3996597#step/openqa_bootstrap/14 shows that openqa-bootstrap tries to add a repository with content "15.6 Beta" in the URL
So, my questions are:
- Does it make sense we test this module in Beta phase?
- Can we un-schedule this test in Beta phase? [I can change the test code to skip this test then]
Observation¶
openQA test in scenario opensuse-15.6-DVD-Updates-x86_64-openqa_bootstrap@64bit fails in
openqa_bootstrap
Test suite description¶
Maintainer: dheidler. Install openQA using openqa-bootstrap script.
Reproducible¶
Fails since (at least) Build 20240308-1
Suggestions¶
- Possibly https://build.opensuse.org/project/show/devel:openQA:Leap:15.6 is the correct build repository that should be used. As necessary to fix tests add according dependencies there to fix
Further details¶
Always latest result in this scenario: latest
Updated by mkittler 9 months ago
This PR should fix it: https://github.com/os-autoinst/openQA/pull/5531
Updated by okurz 9 months ago
mkittler wrote in #note-6:
Not sure how to test this before merging the PR. The test installs the
openQA-bootstrappackage but this package will never have the version from my PR before merging it.
You could test that manually, e.g. using the developer mode of the original failing openQA test scenario and then add the corresponding package from devel:openQA:PR:…. Or you could create a temporary change of os-autoinst-distri-opensuse to install the repository corresponding before the original test flow continues. Or you just get the PR merged, wait for the corresponding package change to reach the relevant product (or submit?) and then test in the original scenario.
Updated by mkittler 9 months ago
I went for modifying the test code. I also created a PR with test code changes to make this a proper workaround: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18908
Updated by mkittler 9 months ago
I created a SR: https://build.opensuse.org/request/show/1159833
There have not been any relevant dependency changes since the last SR (except for the local-npm-registry but that should be fine) so I hope it'll be fine.
Updated by mkittler 9 months ago
The latest job still fails but the package is also still at https://github.com/os-autoinst/openQA/commit/b96c049 despite the SR being accepted.
Updated by mkittler 9 months ago
- Status changed from Feedback to Resolved
The latest job has now the new version and is passing: https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD-Updates&machine=64bit&test=openqa_bootstrap&version=15.6#step/openqa_bootstrap/10