action #109725
closed[timebox: 16h] Investigate script failures on ppc64le
0%
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.
Updated by JRivrain over 2 years ago
- Project changed from openQA Tests (public) to qe-yam
- Category deleted (
Bugs in existing tests)
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
Updated by JRivrain over 2 years ago
- Subject changed from investigate script_run failure to investigate script_run failures on ppc64le
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:
- 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 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
it keeps happening: https://openqa.suse.de/tests/8569078#step/zypper_in/2
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
Incorporated info from https://progress.opensuse.org/issues/109452
Updated by JERiveraMoya over 2 years ago
- Tags deleted (
qe-yast-refinement) - Status changed from New to Workable
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)
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:
- 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 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).
Updated by JERiveraMoya over 2 years ago
- Status changed from In Progress to Workable
- Assignee deleted (
hjluo)
Updated by slo-gin over 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.
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.