action #115259
closed[qe-sap] test fails in update_install
100%
Description
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-SAP-Incidents-Install-ppc64le-qam-incidentinstall-sap@ppc64le-2g fails in
update_install
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build :25428:supportutils-plugin-ha-sap (current job)
Expected result¶
Last good: :25406:curl (or more recent)
Further details¶
Always latest result in this scenario: latest
*Note: this test was restarted and since has passed.
Updated by emiura over 1 year ago
This error is:
Test died: Parsing binaries from SMELT data failed at sle/tests/qam-updinstall/update_install.pm line 120.¶
update_install::run(update_install=HASH(0x564a45508988)) called at /usr/lib/os-autoinst/basetest.pm line 328
eval {...} called at /usr/lib/os-autoinst/basetest.pm line 322
basetest::runtest(update_install=HASH(0x564a45508988)) called at /usr/lib/os-autoinst/autotest.pm line 367
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 367
autotest::runalltests() called at /usr/lib/os-autoinst/autotest.pm line 243
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 243
autotest::run_all() called at /usr/lib/os-autoinst/autotest.pm line 294
autotest::__ANON__(Mojo::IOLoop::ReadWriteProcess=HASH(0x564a44b8b920)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 326
eval {...} called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 326
Mojo::IOLoop::ReadWriteProcess::_fork(Mojo::IOLoop::ReadWriteProcess=HASH(0x564a44b8b920), CODE(0x564a4505d850)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 488
Mojo::IOLoop::ReadWriteProcess::start(Mojo::IOLoop::ReadWriteProcess=HASH(0x564a44b8b920)) called at /usr/lib/os-autoinst/autotest.pm line 296
autotest::start_process() called at /usr/bin/isotovideo line 273
According to Jozef Pupava:
yes, it's because the code is expecting LTSS repo, but not all SAP updates have it
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-incidentinstall-sap
https://openqa.suse.de/tests/9603518#step/update_install/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 openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-incidentinstall-sap
https://openqa.suse.de/tests/9696722#step/update_install/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 84 days if nothing changes in this ticket.
Updated by dzedro over 1 year ago
- Status changed from New to In Progress
Updated by dzedro over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100