action #128150
closed
coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Fix the wickedd.service checking issue
Added by zoecao about 1 year ago.
Updated 12 months ago.
Description
Motivation:
In the wicked test module, it entered command "systemctl status wickedd.service", but for some reasons, it didn't come to the end, see the screenshot 
，
then the test continue to enter the next command so the case failed as this:
https://openqa.suse.de/tests/10953873#step/wicked/1
If changing the command to "systemctl status --no-pager wickedd.service" would resolve the problem.
Files
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: autoupgrade_sles15sp4_pscc_basesys-srv_all_full_auto
https://openqa.suse.de/tests/11022701#step/wicked/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.
- Status changed from New to Workable
- Target version set to Current
The description can't edit, we can add more memory to try to fix this issue, if this can't work then try to investigate the creation job for autoyast-SLES-15-SP4-aarch64-gnome-allpatterns-updated.qcow2 to see whether there are something wrong in the service section.
- Assignee set to tinawang123
- Status changed from Workable to In Progress
tinawang123 wrote:
leli wrote:
I just checked the profile to create the qcow, https://openqa.nue.suse.com/tests/11135455/settings/autoyast_sle15/create_hdd/create_hdd_gnome_allpatterns_aarch64.xml
There is no networking section, I'm not sure this is the root cause while we'd better to try to add it to profile and run a verification.
I updated profile with your suggestion added network information. Still failed: https://openqa.suse.de/tests/11138461#step/wicked/1
To prove there is no relationship with the profile or autoyast creation job, I suggest to create a new qcow with normal interactive way, then if no such issue any more, we need continue to find where is wrong in the profile, if it still has the issue then means something wrong but not in the profile. Please do this without your PR but just clone the failed job to verify the new qcow.
Let's figure out why now is sent to the pager, if other commands behaves the same, some default change?
If we cannot answer those questions asking in our channels in a short time in this ticket, then let's resolve this one and create a new ticket with label [Research: 16h] for example and low priority to answer it.
- Status changed from In Progress to Resolved
- Status changed from Resolved to In Progress
- Priority changed from Normal to Urgent
- Parent task set to #121876
- Related to action #129559: [qe-core][leap15.4]test fails in wicked added
- Related to action #129547: Set networking section with explicit eth0 defined in autoyast profile to avoid complicated output issue for wicked added
- Status changed from In Progress to Resolved
Also available in: Atom
PDF