action #98087
closed
jobs on s390 fail with "Too few arguments for subroutine 'consoles::sshVirtsh::define_and_start'" after OSD deployment on 2021-09-03
Added by Xiaojing_liu over 3 years ago.
Updated almost 3 years ago.
Category:
Regressions/Crashes
Description
Observation¶
jobs fail with
# Test died: {
"args" => [],
"json_cmd_token" => "pPiZtnZT",
"function" => "define_and_start",
"cmd" => "backend_proxy_console_call",
"wantarray" => undef,
"console" => "svirt"
}
Too few arguments for subroutine 'consoles::sshVirtsh::define_and_start' at /usr/lib/os-autoinst/backend/baseclass.pm line 838.
at /usr/lib/os-autoinst/backend/console_proxy.pm line 65.
backend::console_proxy::__ANON__(undef) called at sle/tests/installation/bootloader_zkvm.pm line 78
bootloader_zkvm::run(bootloader_zkvm=HASH(0x10011b8f888)) called at /usr/lib/os-autoinst/basetest.pm line 355
eval {...} called at /usr/lib/os-autoinst/basetest.pm line 349
basetest::runtest(bootloader_zkvm=HASH(0x10011b8f888)) called at /usr/lib/os-autoinst/autotest.pm line 374
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 374
autotest::runalltests() called at /usr/lib/os-autoinst/autotest.pm line 242
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 242
autotest::run_all() called at /usr/lib/os-autoinst/autotest.pm line 298
autotest::__ANON__(Mojo::IOLoop::ReadWriteProcess=HASH(0x1001269bf10)) 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(0x1001269bf10), CODE(0x100133df800)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 477
Mojo::IOLoop::ReadWriteProcess::start(Mojo::IOLoop::ReadWriteProcess=HASH(0x1001269bf10)) called at /usr/lib/os-autoinst/autotest.pm line 300
autotest::start_process() called at /usr/bin/isotovideo line 272
Here is an example: https://openqa.suse.de/tests/7011839#step/bootloader_zkvm/28
After rollbacking the deployment, the jobs didn't have this issue.
- Priority changed from Normal to Urgent
- Target version set to Ready
- Status changed from New to Feedback
- Status changed from Feedback to In Progress
deployment done, called script/openqa-label-all --verbose --openqa-host https://openqa.suse.de --label '* bootloader_zkvm: https://progress.opensuse.org/issues/98087' --module bootloader_zkvm
- Due date set to 2021-09-18
Setting due date based on mean cycle time of SUSE QE Tools
- Assignee changed from okurz to Xiaojing_liu
- Status changed from In Progress to Feedback
The follow-up PR got merged
- Status changed from Feedback to Resolved
There are no reports in #testing and didn't find new fail jobs related to this issue, we consider this was fixed.
- Copied to action #98448: As followup to #98087 tell mergify to only accept changes with 100% patch statement coverage added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: create_hdd_gnome_libyui@svirt-xen-hvm
https://openqa.suse.de/tests/7126583
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
- Estimated time set to 4.00 h
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: create_hdd_gnome_libyui@svirt-xen-hvm
https://openqa.suse.de/tests/8162697
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
- Status changed from Resolved to Feedback
- Priority changed from Urgent to High
Please check the soft-fail reference
- Status changed from Feedback to Resolved
re https://openqa.suse.de/tests/8162697
The comment was:
syrianidou_sofia wrote 2022-02-14 21:24:56 +0000
poo#98087
(Automatic takeover from t#7014938)
I deleted it. The test failure had nothing to do with this issue.
(The linked takeover job was already gone)
Also available in: Atom
PDF