action #120109


[sle15sp5] containers testing is blocked due to failing create_hdd_autoyast_containers

Added by mloviska over 1 year ago. Updated over 1 year ago.

Bugs in existing tests
Target version:
Start date:
Due date:
% Done:


Estimated time:



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:

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

Expected result

Last good: 24.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by mdati over 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to mdati

Looking at the failing test, it results that theSLE_15_SP5/ dir and related repo file and any other subdata are missing in OBS under CA in:

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.

Actions #2

Updated by mdati over 1 year ago

The expexted directory and repo is now present in OBS; tests restarted.

Actions #3

Updated by mdati over 1 year ago

  • Status changed from In Progress to Resolved

The container tests 'create_hdd_autoyast_containers' for sle15sp5 has been correctly triggered and now passed and unblocked the other dependant tests, also running.
Issue resolved.

Actions #4

Updated by openqa_review over 1 year 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:

  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.

Actions #5

Updated by mdati over 1 year ago

After the test create_hdd_autoyast_containers failed, this poo was referenced into its comments and the status automaticaly changed from Resolved to Feedback.

Looking at that first test 10194847, again the SUSE:CA.repo was not reachable(or not present) at runtime.
Restarted today that test, it pass, see

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 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") ...
Actions #6

Updated by mdati over 1 year ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF