Project

General

Profile

Actions

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 11 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
Start date:
2023-04-21
Due date:
% Done:

0%

Estimated time:

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


Related issues 2 (0 open2 closed)

Related to openQA Tests - action #129559: [qe-core][leap15.4]test fails in wickedResolvedrfan12023-05-18

Actions
Related to qe-yam - action #129547: Set networking section with explicit eth0 defined in autoyast profile to avoid complicated output issue for wickedResolvedcoolgw2023-05-18

Actions
Actions #1

Updated by openqa_review 12 months ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #2

Updated by leli 12 months ago

  • 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.

Actions #3

Updated by tinawang123 12 months ago

  • Assignee set to tinawang123
Actions #4

Updated by tinawang123 12 months ago

  • Status changed from Workable to In Progress
Actions #6

Updated by leli 12 months ago

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.

Actions #7

Updated by tinawang123 12 months ago

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

Actions #8

Updated by leli 11 months ago

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.

Actions #9

Updated by JERiveraMoya 11 months ago

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.

Actions #10

Updated by tinawang123 11 months ago

  • Status changed from In Progress to Resolved
Actions #11

Updated by JERiveraMoya 11 months ago

  • Status changed from Resolved to In Progress
  • Priority changed from Normal to Urgent
  • Parent task set to #121876
Actions #12

Updated by JERiveraMoya 11 months ago

  • Related to action #129559: [qe-core][leap15.4]test fails in wicked added
Actions #13

Updated by leli 11 months ago

  • Related to action #129547: Set networking section with explicit eth0 defined in autoyast profile to avoid complicated output issue for wicked added
Actions #14

Updated by JERiveraMoya 11 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF