QA (public) » openQA Project (public) » openQA Tests (public) » ALP

In the previous run, I see that it failed at a different stage:
https://openqa.opensuse.org/tests/2955255#step/cockpit_service/16

Retrieving: libopus0-1.3.1-4.8.aarch64.rpm [error]
Download (curl) error for 'https://download.opensuse.org/repositories/SUSE:/ALP/standard/aarch64/libopus0-1.3.1-4.8.aarch64.rpm':
Error code: Curl error 92
Error message: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

Could this be due to aarch64 repo changing while tests are running? (just guessing)

jlausuch wrote:

In the previous run, I see that it failed at a different stage:
https://openqa.opensuse.org/tests/2955255#step/cockpit_service/16

Retrieving: libopus0-1.3.1-4.8.aarch64.rpm [error]
Download (curl) error for 'https://download.opensuse.org/repositories/SUSE:/ALP/standard/aarch64/libopus0-1.3.1-4.8.aarch64.rpm':
Error code: Curl error 92
Error message: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

Could this be due to aarch64 repo changing while tests are running? (just guessing)

I do not think so, because it would rather throw an "RPM not found" error.
x86_64 is also affected by the way.

Problem solved?
https://openqa.opensuse.org/tests/2959110#step/cockpit_service/16

The issue might be due to the mirror infrastructure or inconsistent state of the local zypper cache. I see the upstream feature request for zypper https://github.com/openSUSE/zypper/issues/420 related which should help but it does not look like the idea is accepted nor will be implemented anytime soon. But of course you can retry within the test code, e.g. explicitly call zypper refresh and then again transactional-update to pick up the updated metadata.

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

This bug is still referenced in a failing openQA test: alp_default
https://openqa.opensuse.org/tests/3044446#step/cockpit_service/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.

This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.