Project

General

Profile

Actions
Copy link

action #109725

closed

[timebox: 16h] Investigate script failures on ppc64le

Added by JRivrain over 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Target version:
Current
Start date:
2022-04-08
Due date:
% Done:

0%

Estimated time:

Description

Observation

The test regularly failed several times recently trying to write "zypper lr -d". In each case observed it fails to write the final "r" in zypper, see also hereand here

openQA test in scenario sle-15-SP4-Full-ppc64le-offline_install+skip_registration@ppc64le fails in
zypper_in

Modules validate_addon_extension_repo_http and validate_addon_extension_repo_ftp fail sporadically in validate_repo_properties().
The failure occurs during inside script_ouput stage of parse_repo_data() and can be seen here, but it is most likely not related to the bsc#1193214 failure (seen here).

In autoinst-log.txt we see command 'curl -f -v http://10.0.2.2:20063/k2w1yCaJzocsF6Je/current_script > /tmp/scriptC_1nj.sh' failed at /usr/lib/os-autoinst/testapi.pm line 953. but the command is different in the console before the failure

In general both issues seem the same problem, mistyping not be able to reach the SUT with the the characters sent.

Acceptance criteria

AC1: Investigate root cause (previous zypper ref?) and how could be mitigated.

Further details

Perhaps the zypper ref in this slow arch is producing this issue somehow. We could check how does it look the load in the system after this command.

Actions
Copy link
 #1

Updated by JRivrain over 2 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
Actions
Copy link
 #2

Updated by JRivrain over 2 years ago

The problem is also visible in other places as https://openqa.suse.de/tests/8493080#step/verify_default_target/4

Actions
Copy link
 #3

Updated by JRivrain over 2 years ago

  • Subject changed from investigate script_run failure to investigate script_run failures on ppc64le
Actions
Copy link
 #4

Updated by openqa_review over 2 years 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_install+skip_registration
https://openqa.suse.de/tests/8569078#step/zypper_in/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
Copy link
 #5

Updated by JERiveraMoya over 2 years ago

  • Tags set to qe-yast-refinement
  • Subject changed from investigate script_run failures on ppc64le to [timebox: 8h] Investigate script_run failures on ppc64le
  • Target version set to Current
Actions
Copy link
 #6

Updated by JERiveraMoya over 2 years ago

  • Description updated (diff)
Actions
Copy link
 #7

Updated by JERiveraMoya over 2 years ago

  • Subject changed from [timebox: 8h] Investigate script_run failures on ppc64le to [timebox: 16h] Investigate script failures on ppc64le
  • Description updated (diff)
  • Priority changed from Normal to High
Actions
Copy link
 #8

Updated by JERiveraMoya over 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions
Copy link
 #9

Updated by geor over 2 years ago

please check if this failure is also related to the reported issue. (This one also fails inside script_output, as seen in the autoinst-log.txt)

Actions
Copy link
 #10

Updated by openqa_review over 2 years 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_install+skip_registration
https://openqa.suse.de/tests/8736744#step/zypper_in/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
Copy link
 #11

Updated by okurz over 2 years ago

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. First reminder: Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days).

Actions
Copy link
 #12

Updated by hjluo over 2 years ago

  • Assignee set to hjluo
Actions
Copy link
 #13

Updated by hjluo over 2 years ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #14

Updated by JERiveraMoya over 2 years ago

  • Status changed from In Progress to Workable
  • Assignee deleted (hjluo)
Actions
Copy link
 #15

Updated by slo-gin about 2 years ago

This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #16

Updated by JERiveraMoya about 2 years ago

  • Status changed from Workable to Rejected

We will be moving progressively to PowerVM, all this problems are PowerKVM-related ones.

Actions
Copy link

Also available in: Atom PDF