[sle15sp5] containers testing is blocked due to failing create_hdd_autoyast_containers
openQA test in scenario sle-15-SP5-Online-aarch64-create_hdd_autoyast_containers@aarch64-virtio fails in
For some reason, the
install_update test case got into GA jobs.
Expected run: https://openqa.suse.de/tests/9563666
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Fails since (at least) Build 25.1
Last good: 24.1 (or more recent)
Always latest result in this scenario: latest
Updated by mdati about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to mdati
Looking at the failing test, it results that the
SLE_15_SP5/ dir and related repo file and any other subdata are missing in OBS under CA in: http://download.suse.de/ibs/SUSE:/CA/
That repo has to be created, so that the test will go on: a 'SUES:CA' Mantainer has been contacted.
In addition let we note that the named failing
container module, after
autoyast executed, in the old passing builds is missing : it was not present yet, so it was not executed in builds from Build24.1 and older.
Updated by openqa_review 12 months 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: create_hdd_autoyast_containers
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.
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
After the test create_hdd_autoyast_containers failed, this poo was referenced into its comments and the status automaticaly changed from Resolved to Feedback.
For future considerations, in order to better distinguish cases of file missing or url not reachable instead, it could be useful eventually to add in
install_updates.pm before of the
zypper -n ar ... command , a check loop to verify if the url is not reachable and stop the test here (die), like:
... assert_script_run("ping -4 -c1 -W 20 download.suse.de") ...