action #151246
open[opensuse][ppc64le] test fails in updates_packagekit_kde on 15.2 image opensuse-15.2-ppc64le-GM-kde@ppc64le.qcow2
0%
Description
Observation¶
I created bug for it, but then I realized the test is using Leap 15.2
I assume the test should use newer Leap version.
https://bugzilla.opensuse.org/show_bug.cgi?id=1217369
openQA test in scenario opensuse-15.4-Container-Image-ppc64le-container_image_on_leap15.2_host@ppc64le fails in
updates_packagekit_kde on 15.4
updates_packagekit_kde on 15.5
Also another test but same issue with image opensuse-15.3-ppc64le-160.3-textmode@ppc64le.qcow2
https://openqa.opensuse.org/tests/3745089 on openSUSE Leap 15.4 Images
https://openqa.opensuse.org/tests/3745155 on openSUSE Leap 15.5 Images
Reproducible¶
Fails since (at least) Build 91.5
Expected result¶
Last good: 91.3 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dzedro 5 months ago
- Subject changed from [opensuse][15.4][ppc64le] test fails in updates_packagekit_kde on 15.2 image opensuse-15.2-ppc64le-GM-kde@ppc64le.qcow2 to [opensuse][ppc64le] test fails in updates_packagekit_kde on 15.2 image opensuse-15.2-ppc64le-GM-kde@ppc64le.qcow2
- Description updated (diff)
Updated by openqa_review 5 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: container_image_on_leap15.2_host
https://openqa.opensuse.org/tests/3754379#step/updates_packagekit_kde/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 dzedro 5 months ago
- File Screenshot_2023-12-08_09-29-17.png added
The tricky scheduling of ppc64le via x86_64 is for some reason unstable.
There was change in variable name [1], I guess since then the wrong schedule of container tests on ppc64le started.
I don't see what could in that PR cause this issue, the test schedule unstability was there also before [2] or
there were another changes in backend, IDK.
When I tried to force schedule the test with CONTAINER_RUNTIME=podman,docker test was failing cache failure: Failed to rsync tests: exit code 255.
For me the test was correctly scheduled when I used CASEDIR.
It's kind of impossible for me to debug this, I just created PR [3] to add CASEDIR.
@favogt @dimstar maybe you have better idea.
[1] https://github.com/os-autoinst/opensuse-jobgroups/pull/389
[2] https://openqa.opensuse.org/tests/3725151#next_previous
[3] https://github.com/os-autoinst/opensuse-jobgroups/pull/398
Updated by dzedro 5 months ago
- Status changed from New to Feedback
I guess worker was fixed. https://suse.slack.com/archives/C02CANHLANP/p1702285222592179