action #100919
closed
test fails in addon_products_via_SCC_yast2: alt-b didn't reach the SUT
Added by JERiveraMoya over 2 years ago.
Updated over 2 years ago.
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-ppc64le-sles+sdk+proxy_SCC_via_YaST@ppc64le-2g fails in
addon_products_via_SCC_yast2
Seems that alt-b was lost and we don't navigate back. Also doesn't look sporadic.
Test suite description¶
Maintainer: jpupava
Add add-on via YaST control center directly
https://progress.opensuse.org/issues/16402
Reproducible¶
Fails since (at least) Build 36.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Current
- Status changed from Workable to In Progress
- Assignee set to rainerkoenig
- Status changed from In Progress to Blocked
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sles+sdk+proxy_SCC_via_YaST@ppc64le-2g
https://openqa.suse.de/tests/7655946
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
- Status changed from Blocked to Closed
Let's close it to avoid further remainder from automation, as it is clear it is related with the bug and our investigation was done.
Also available in: Atom
PDF