action #121555
closed
Multimachine test network setup fails fails in yast2_nfs_client and others
Added by pcervinka about 2 years ago.
Updated over 1 year ago.
Description
Observation¶
openQA test in scenario sle-15-SP5-Online-ppc64le-yast2_nfs_v3_client@ppc64le fails in
yast2_nfs_client
Test suite description¶
Multi-machine NFSv3 test with Yast. Maintainer: jrivrain@suse.com
Reproducible¶
Fails since (at least) Build 58.1 (current job)
Expected result¶
Last good: 52.4 (or more recent)
Further details¶
Always latest result in this scenario: latest
Test died: Can't use an undefined value as an ARRAY reference at sle/lib/mm_network.pm line 122.
mm_network::configure_static_dns(HASH(0x10008c28b18), "is_nm", "") called at sle/lib/mm_network.pm line 223
mm_network::setup_static_mm_network("10.0.2.102/24") called at sle/tests/console/yast2_nfs_client.pm line 37
yast2_nfs_client::run(yast2_nfs_client=HASH(0x1000bc11918)) called at /usr/lib/os-autoinst/basetest.pm line 339
eval {...} called at /usr/lib/os-autoinst/basetest.pm line 333
basetest::runtest(yast2_nfs_client=HASH(0x1000bc11918)) called at /usr/lib/os-autoinst/autotest.pm line 387
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 387
autotest::runalltests() called at /usr/lib/os-autoinst/autotest.pm line 244
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 244
autotest::run_all() called at /usr/lib/os-autoinst/autotest.pm line 295
autotest::__ANON__(Mojo::IOLoop::ReadWriteProcess=HASH(0x1000c45be68)) 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(0x1000c45be68), CODE(0x1000c8d2ee0)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 488
Mojo::IOLoop::ReadWriteProcess::start(Mojo::IOLoop::ReadWriteProcess=HASH(0x1000c45be68)) called at /usr/lib/os-autoinst/autotest.pm line 297
autotest::start_process() called at /usr/bin/isotovideo line 243
- Status changed from New to In Progress
- Assignee set to pdostal
- Project changed from openQA Tests (public) to qe-yam
- Category deleted (
Bugs in existing tests)
- Status changed from In Progress to Feedback
Waiting some time for some test runs.
Hello Sofia, the run you mentioned is three days old but my pull request has been merged two days ago. We need to wait for another run.
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.
It keeps failing sporadically after the fix is merged: https://openqa.suse.de/tests/10441871#next_previous
As the failure happens only with ppc64le KVM (unsupported virtualization) we will move it to development group where we don't plan to fix it in the near future.
- Status changed from Feedback to Resolved
- Assignee changed from pdostal to syrianidou_sofia
- Priority changed from High to Low
- Target version set to Current
- Related to action #124014: Watch for powerpc KVM yast2_nfs_v3/4_server/client if network issues still persist added
- Status changed from Resolved to In Progress
- Assignee changed from syrianidou_sofia to pdostal
- Project changed from qe-yam to openQA Tests (public)
- Target version deleted (
Current)
@pdostal, please assign to your squad this ticket, Yam squad does not plan to work in the near future in ppc64le Power KVM due to it is unsupported virtualization.
Set label for your squad or whatever subproject you use.
- Project changed from openQA Tests (public) to qe-yam
JERiveraMoya wrote:
@pdostal, please assign to your squad this ticket, Yam squad does not plan to work in the near future in ppc64le Power KVM due to it is unsupported virtualization.
Set label for your squad or whatever subproject you use.
discussed with Pavel that we keep it in Yam subproject but without Target version, so it doesn't show in our Sprint backlog and he still can help and request our assistance any time. thanks!
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: SAPHanaSR_ScaleUp_PerfOpt_supportserver
https://openqa.suse.de/tests/10563425#step/setup/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.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: ha_beta_supportserver
https://openqa.suse.de/tests/10599261#step/setup/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 56 days if nothing changes in this ticket.
- Assignee deleted (
pdostal)
I agree with Lumir. This is probably worker-specific issue.
- Status changed from In Progress to Rejected
Also available in: Atom
PDF