action #121618
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Fix the unexpected return value for dhcp-server of install_service
0%
Description
Motivation¶
Some test failed in migration regression job group for this issue:
https://openqa.nue.suse.com/tests/10091596#step/install_service/80
https://openqa.nue.suse.com/tests/10091598#step/install_service/80
https://openqa.nue.suse.com/tests/10091601#step/install_service/80
It failed for the ip interface is on 'UNKNOWN' state while not 'UP', bug to track it https://bugzilla.suse.com/show_bug.cgi?id=1208832
We can exclude dhcp-server to avoid this issue on powerVM.
INCLUDE_SERVICES sshd,firewalld,apache2,dhcp-server,bind,autofs,vsftpd
Acceptance criteria¶
AC1: Exclude dhcp-server from powerVM service check list.
Updated by coolgw over 1 year ago
It seems ip interface not up? Suggest add "ip addr" in code to show what's wrong there.
Updated by openqa_review over 1 year ago
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.
Updated by openqa_review about 1 year ago
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.
Updated by JERiveraMoya about 1 year ago
- 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.
Updated by geor about 1 year ago
I believe this ticket is better suited for the openqa tools team.
Updated by JERiveraMoya about 1 year ago
- 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
Updated by rainerkoenig about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to rainerkoenig
Updated by leli about 1 year ago
Got the confirm info from bug https://bugzilla.suse.com/show_bug.cgi?id=1208832 ：
Michal Suchanek 2023-03-02 12:04:11 UTC
It's normal, drivers are not required to set the state.
Some do, some don't.
Updated by rainerkoenig about 1 year ago
Created MR#245 which should fix the issue.