QA » openQA Project » openQA Tests

We checked the issue shortly during the SUSE QE Tools estimation call 2023-01-26 and we have found the test scenario to be very stable, not reproducing the issue for multiple hundreds of jobs. We assume it might be a race condition in product behaviour which we do not need to care about right now assuming it will not happen again. If it does then with the additional data we can look into it in more detail.

It unfortunately happened again: https://openqa.opensuse.org/tests/3107691
This is not the only occurrence. There were 8 occurrences within the last 24 hours.

mkittler wrote:

It unfortunately happened again: https://openqa.opensuse.org/tests/3107691
This is not the only occurrence. There were 8 occurrences within the last 24 hours.

Confirmed. And it happens here:

retry -s 30 -- sh -c "zypper -n --gpg-auto-import-keys ref && zypper --no-cd -n in openQA-worker"

So I suppose we need to retry harder here as well, like we've done in #123106.

Setting due date based on mean cycle time of SUSE QE Tools

jbaier_cz wrote:

mkittler wrote:

I'm not suggesting they're the same error. The test I've been looking at was https://openqa.opensuse.org/tests/3107691 which is about the GNOME auth dialog. The other 7 tests might not all be about this issue because I've just checked a few of them (and assumed for the rest they'd be the same as the failing module is the same).

Cris created a comment in the openQA job linking this issue to the other failure, so the question was directed more to @cdywan rather than you. The GNOME auth dialog is in the worker module, the other one (zypper and repository problem) is in openqa_worker. On the other hand, both of them are sporadic and irritating.

Sorry, I didn't realize there was another error message. The other jobs I was checking had the zypper issue, and just now checking the original one here again I see it. The other link doesn't point to a specific job.

Maybe we need another ticket? Or otherwise I would unassign here for now. At least I'm not clear what the cause of the authentication issue is for now.

So feel free to grab it if you do have a better idea, otherwise I'll investigate it further on the next opportunity.

It looks like simple packagekit issue - > after installation openqa-worker was released new snapshot / update in repos used by test and then packagekit asked for root password via gnome auth dialog, which broke test. --> I think there is simple workaround -> disable packagekit on SUT.

Setting due date based on mean cycle time of SUSE QE Tools

merged

https://openqa.opensuse.org/tests/3149603#step/worker/4 looks like this doesn't cut it.

so .. there is another trigger :(

merged , we will see :D

Always latest result in this scenario: latest

This looks all green, so I guess we're good