QA » openQA Project » openQA Tests » qe-yam

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

This bug is still referenced in a failing openQA test: yast2_gui
https://openqa.suse.de/tests/13021643#step/yast2_security/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.

Looks like an sporadic problem of pending load of the YaST modules after closing having issues opening it again (we have seen those kind of bugs in the past).

Some suggestion could be to run it separately without the rest of test modules, it might be a bug that something is stuck, but we need to narrow the reproducibility for developers to be able to fix it if we file a bug. Also to see if manually happens somehow.

I noticed we couldn't find the ticket because of "Blocked" status (it is not displayed on purpose in our Sprint backlog).
Is it fine if I/you set to Workable and unassigned or you plan more investigation? thanks.

JERiveraMoya wrote in #note-7:

Looks like an sporadic problem of pending load of the YaST modules after closing having issues opening it again (we have seen those kind of bugs in the past).

Some suggestion could be to run it separately without the rest of test modules, it might be a bug that something is stuck, but we need to narrow the reproducibility for developers to be able to fix it if we file a bug. Also to see if manually happens somehow.

I noticed we couldn't find the ticket because of "Blocked" status (it is not displayed on purpose in our Sprint backlog).
Is it fine if I/you set to Workable and unassigned or you plan more investigation? thanks

This: https://openqa.suse.de/tests/13187869 is a different problem than the sporadic failure that is the subject of this ticket. And currently, it is not sporadic, it always happens.

Some suggestion could be to run it separately without the rest of test modules

I obviously did that ! The test run I posted with all modules included is to make sure the exclusion of some modules - like consoletest_setup - is not the cause of the failure.

As-is, it is not "workable" currently, since the described issue cannot be reproduced, and another issue is seen instead. It is not likely to be a product bug, as the same test passed earlier on the same build without that failure.

Blocked by https://progress.opensuse.org/issues/153169