action #121618
closed
- Description updated (diff)
It seems ip interface not up? Suggest add "ip addr" in code to show what's wrong there.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: offline_sles15sp3_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full_pre
https://openqa.suse.de/tests/10256084#step/install_service/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.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: offline_sles15sp2_ltss_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full_pre
https://openqa.suse.de/tests/10468156#step/install_service/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 88 days if nothing changes in this ticket.
- Tags set to qe-yam-refinement
I will do some pair-debugging with @lemon to figure out what happen in that point and refine the ticket better.
I believe this ticket is better suited for the openqa tools team.
- Description updated (diff)
- Tags deleted (
qe-yam-refinement)
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Current
- Parent task set to #121876
- Status changed from Workable to In Progress
- Assignee set to rainerkoenig
Created MR#245 which should fix the issue.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF