action #160427
closed[qe-core][functional]test fails in t16_bridge_ifreload_physical
0%
Description
Description¶
As kindly update from Clemens Famulla-Conrad, this is an known issue but seems the fix may not check into sle15sp6 GA.
Workaround as below:
openqa-clone-job --within-instance https://openqa.suse.de 14304917 WICKED_REPO='https://download.suse.de/ibs/home:/wicked-maintainers:/sle15-sp6:/last/SLE_15_SP6/home:wicked-maintainers:sle15-sp6:last.repo'
yes t16_bridge_ifreload_physical is failing from time to time but it look failing more stable now :thinking:. The PR which address this issue is: https://github.com/openSUSE/wicked/pull/990 + https://github.com/openSUSE/wicked/pull/1014
Unfortunately we didn't made it ready for SLE15-SP6:GA, it will be an update. it was just to riski for such a big change in last minute.
Is it easy possible to you just give it a try with https://build.suse.de/package/show/home:wicked-maintainers:sle15-sp6:last/wicked ? This will be the packages which goes to SLE15-SP5:Update
For more information, please refer to https://bugzilla.suse.com/show_bug.cgi?id=1205604
Observation¶
openQA test in scenario sle-15-SP6-Online-x86_64-wicked_startandstop_sut@64bit fails in
t16_bridge_ifreload_physical
Test suite description¶
Startandstop wicked tests Maintainer : asmorodskyi@suse.de, jalausuch@suse.com , cfamullaconrad@suse.de
Reproducible¶
Fails since (at least) Build 62.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by mgrifalconi about 2 months ago
Is it just about waiting for the fix to be implemented or should we edit the test to add the extra repo?
Updated by rfan1 about 2 months ago
mgrifalconi wrote in #note-1:
Is it just about waiting for the fix to be implemented or should we edit the test to add the extra repo?
Thanks Michael,
I think we can leave the failed test here since the fix will not be in GM release,
However, I think we can add the same test to MU https://openqa.suse.de/admin/job_templates/412? once the fix is ready in updates repo
[I just copied the sle15sp5 cases and changed the name to sle15sp6.]
Updated by rfan1 about 1 month ago
- Status changed from New to Workable
- Assignee set to rfan1
Updated by openqa_review 29 days ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: wicked_startandstop_sut
https://openqa.suse.de/tests/14610586#step/t16_bridge_ifreload_physical/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 rfan1 27 days ago
Tests have been added to https://openqa.suse.de/admin/job_templates/564?
Updated by openqa_review 7 days ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: wicked_startandstop_sut
https://openqa.suse.de/tests/14610586#step/t16_bridge_ifreload_physical/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.