QA » openQA Project » openQA Tests

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: offline_sles15sp1_pscc_basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full
https://openqa.suse.de/tests/3916227

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"
3. The label in the openQA scenario is removed

error part seems change, but we still using this ticket tracking this.
https://openqa.suse.de/tests/3928548#step/zypper_lifecycle/1

This was caused by "zypper lifecycle" command timedout. we can fist fix this.

[2020-02-26T23:40:19.256 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-02-26T23:40:19.257 UTC] [debug] <<< testapi::type_string(string="zypper lifecycle\n", max_interval=250, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2020-02-26T23:40:19.876 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-02-26T23:40:19.877 UTC] [debug] <<< testapi::send_key(key="ctrl-d", do_wait=0, wait_screen_change=0)
[2020-02-26T23:40:20.214 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-02-26T23:40:20.215 UTC] [debug] <<< testapi::type_string(string="(echo AwZR8; bash -eox pipefail /tmp/scriptAwZR8.sh ; echo SCRIPT_FINISHEDAwZR8-\$?-) | tee /dev/ttyAMA0\n", max_interval=250, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2020-02-26T23:40:24.637 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-02-26T23:40:24.638 UTC] [debug] <<< testapi::wait_serial(timeout=300, record_output=1, buffer_size=undef, no_regex=0, regexp="SCRIPT_FINISHEDAwZR8-\d+-", expect_not_found=0, quiet=undef)
[2020-02-26T23:45:26.636 UTC] [debug] >>> testapi::wait_serial: SCRIPT_FINISHEDAwZR8-\d+-: fail
[2020-02-26T23:45:26.637 UTC] [debug] script timeout: zypper lifecycle at /usr/lib/os-autoinst/testapi.pm line 1104.

Test died: script timeout: zypper lifecycle at /usr/lib/os-autoinst/testapi.pm line 1104

[2020-03-11T09:08:55.778 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-03-11T09:08:55.778 UTC] [debug] <<< testapi::type_string(string="cat - > /tmp/scriptAwZR8.sh;\n", max_interval=250, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2020-03-11T09:08:56.885 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-03-11T09:08:56.886 UTC] [debug] <<< testapi::type_string(string="zypper lifecycle\n", max_interval=250, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2020-03-11T09:08:57.478 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-03-11T09:08:57.478 UTC] [debug] <<< testapi::send_key(key="ctrl-d", wait_screen_change=0, do_wait=0)
[2020-03-11T09:08:57.816 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-03-11T09:08:57.816 UTC] [debug] <<< testapi::type_string(string="(echo AwZR8; bash -eox pipefail /tmp/scriptAwZR8.sh ; echo SCRIPT_FINISHEDAwZR8-\$?-) | tee /dev/ttyAMA0\n", max_interval=250, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2020-03-11T09:09:02.056 UTC] [debug] tests/console/zypper_lifecycle.pm:43 called testapi::script_output
[2020-03-11T09:09:02.057 UTC] [debug] <<< testapi::wait_serial(quiet=undef, buffer_size=undef, timeout=300, record_output=1, expect_not_found=0, regexp="SCRIPT_FINISHEDAwZR8-\d+-", no_regex=0)
[2020-03-11T09:14:03.824 UTC] [debug] >>> testapi::wait_serial: SCRIPT_FINISHEDAwZR8-\d+-: fail
[2020-03-11T09:14:03.825 UTC] [debug] script timeout: zypper lifecycle at /usr/lib/os-autoinst/testapi.pm line 1104.

you can see it take 09:14:03 - 09:08:55 which cost 6 minutes without return. so we think/verified 9 minutes will be OK.

the syntax error is that we did't handle this kind of scenario.

for repo in (System Packages) ; do zypper -n -x se -t package -i -s -r $repo ; done | grep name= | head -n 1
bash: syntax error near unexpected token `('

which should be:

for repo in "(System Packages)"; do zypper -n -x se -t package -i -s -r $repo ; done | grep name= | head -n 1

[2020-03-11T05:42:48.888 CET] [debug] <<< testapi::wait_serial(timeout=300, record_output=1, buffer_size=undef, no_regex=0, regexp="SCRIPT_FINISHEDAwZR8-\d+-", quiet=undef, expect_not_found=0)

solvable-list>
solvable status="installed" name="389-ds" kind="package" edition="1.4.2.8~git0.3aaa3e820-1.9" arch="s390x" repository="(System Packages)"/>
solvable status="installed" name="GeoIP" kind="package" edition="1.6.12-4.17" arch="s390x" repository="(System Packages)"/>
solvable status="installed" name="GeoIP-data" kind="package" edition="1.6.12-4.17" arch="noarch" repository="(System Packages)"/>
solvable status="installed" name="Mesa" kind="package" edition="19.3.4-44.6" arch="s390x" repository="(System Packages)"/>
solvable status="installed" name="Mesa-dri" kind="package" edition="19.3.4-44.9" arch="s390x" repository="(System Packages)"/>
solvable status="installed" name="Mesa-libEGL1" kind="package" edition="19.3.4-44.6" arch="s390x" repository="(System Packages)"/>
solvable status="installed" name="Mesa-libGL1" kind="package" edition="19.3.4-44.6" arch="s390x" repository="(System Packages)"/>

SCRIPT_FINISHED708tO-0-
[2020-03-11T05:43:14.495 CET] [debug] >>> testapi::wait_serial: SCRIPT_FINISHED708tO-\d+-: ok

reproduce Aarch64 at: https://openqa.nue.suse.com/tests/3984081

this issue just timeout on aarch64 I've set timeout to 1200 and it still fails.

Reproduce on S390x at: https://openqa.nue.suse.com/tests/3984089

this is actually a s390x bug bsc#1166549

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: online_sles15_pscc_lp-basesys-srv-desk-dev-contm-lgm-wsm_all_full
https://openqa.suse.de/tests/4083635

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"
3. The label in the openQA scenario is removed

on a real machine we run this cli with 2 modules.

ps64vt1065:~ # time zypper lifecycle

Product end of support

Codestream: SUSE Linux Enterprise Server 15 2028-07-30
SUSE Linux Enterprise Server 15 SP2 n/a*

Module end of support

Containers Module 2020-06-29
Legacy Module 2021-07-30
Python 2 Module 2021-07-30
Desktop Applications Module n/a*
Public Cloud Module n/a*
Web and Scripting Module n/a*
Development Tools Module n/a*
Basesystem Module n/a*
Server Applications Module n/a*

No packages with end of support different from product.

*) See https://www.suse.com/lifecycle for latest information

real 0m6.184s
user 0m2.676s
sys 0m0.225s

latest run with a bigger timeout value=1600 http://openqa.suse.de/t4138621 still timeout at wait_serial

add script_run 'zypper lifecycle' to verify the timeout

http://openqa.suse.de/t4165134

It shows that the zypper lifecycle return error with can't create metadata cache directory.
the metadata cache needs be built for all modules, whith is a known bug

#P5 Bug 1166549 - [Migration] [Build 155.1] openQA test fails in zypper_lifecycle on S390x - zypper lifecycle error with 'Error building the cache'
http://149.44.176.58/tests/4165134#step/zypper_lifecycle/4

get the error log with diag:

• my $overview = script_output 'zypper lifecycle', 300;
• diag '=================================';
• my $out = script_output("zypper lifecycle", proceed_on_failure => 1);
• diag "zypper lifecycle output: $out";
• diag '=================================';

http://openqa.suse.de/t4166032
http://openqa.suse.de/t4166033