action #65058
closed[qe-core][functional][xen-hvm] test fails in user_defined_snapshot - Machine didn't shut down
Added by SLindoMansilla about 4 years ago. Updated almost 3 years ago.
100%
Description
Obvervations¶
record_info 'Snapshot created', 'booting the system into created snapshot';
power_action('reboot', keepconsole => 1, observe => is_remote_backend);
$self->wait_grub(bootloader_time => 250);
power_action failed to reboot.
Reproducible¶
- In scenario sle-15-SP2-Online-x86_64-extra_tests_gnome@svirt-xen-hvm
- Fails since Build [167.5]
- Current occurrence: 168.1
Expected result¶
Last good: 164.1
Further details¶
Always latest result in this scenario: latest
Updated by okurz about 4 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/4125589
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"
- The label in the openQA scenario is removed
Updated by okurz about 4 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/4125589
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"
- The label in the openQA scenario is removed
Updated by okurz about 4 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/4187229
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"
- The label in the openQA scenario is removed
Updated by okurz almost 4 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/4248037
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"
- The label in the openQA scenario is removed
Updated by SLindoMansilla almost 4 years ago
- Description updated (diff)
- Category changed from Bugs in existing tests to Spike/Research
- Status changed from New to Workable
- Assignee set to szarate
- Target version set to Milestone 30
- Estimated time set to 42.00 h
Updated by openqa_review over 3 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: extra_tests_gnome@svirt-xen-pv
https://openqa.suse.de/tests/4576538
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"
- The label in the openQA scenario is removed
Updated by okurz over 3 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/4757562
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"
- The label in the openQA scenario is removed
Updated by szarate over 3 years ago
- Assignee deleted (
szarate) - Priority changed from Normal to High
Updated by okurz over 3 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/4901680
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"
- The label in the openQA scenario is removed
Updated by tjyrinki_suse over 3 years ago
- Subject changed from [functional][u][xen-hvm] test fails in user_defined_snapshot - Machine didn't shut down to [qe-core][functional][xen-hvm] test fails in user_defined_snapshot - Machine didn't shut down
Updated by okurz over 3 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/5025409
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"
- The label in the openQA scenario is removed
Updated by okurz over 3 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/5131847
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"
- The label in the openQA scenario is removed
Updated by okurz over 3 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: extra_tests_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/5190071
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"
- The label in the openQA scenario is removed
Updated by punkioudi over 3 years ago
- % Done changed from 0 to 20
Draft PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11736/files
By removing the observe argument(for which I don't see a significant purpose of existing), reboot works as expected and eventually the test passes.
Updated by punkioudi over 3 years ago
Test now fails for scenario sle-15-SP2-Online-x86_64-extra_tests_gnome@svirt-xen-pv in a different place : https://openqa.suse.de/tests/5305271#step/user_defined_snapshot/39
The function wait_grub is called during that step, which is not the case for this machine.
New PR will be prepared to cover this case too.
Updated by punkioudi over 3 years ago
- % Done changed from 20 to 50
Updated by tjyrinki_suse about 3 years ago
- Status changed from Workable to In Progress
Updated by punkioudi about 3 years ago
The last runs of extra_tests_gnome@svirt-xen-hvm are cancelled due to a previous failing job, so I ran again one test with git-refspec, which passes : https://openqa.suse.de/tests/5469544
We can keep though the ticket open, until the test passes consequently in osd.
Updated by szarate about 3 years ago
So I think that making the machine to soft-fail when it couldn't shut down, and force the shutdown via acpi or something in the backend https://openqa.suse.de/tests/5462020#step/shutdown/19
Updated by punkioudi about 3 years ago
@szarate should we then open a new progress issue for that, as this fail happens in a different place than the current in the description?
Updated by tjyrinki_suse about 3 years ago
- Target version changed from Milestone 30 to Ready
Updated by tjyrinki_suse about 3 years ago
- Target version changed from Ready to QE-Core: Ready
Updated by tjyrinki_suse about 3 years ago
- Target version changed from QE-Core: Ready to Ready
Updated by szarate about 3 years ago
- Target version changed from Ready to QE-Core: Ready
Updated by tjyrinki_suse about 3 years ago
- Target version deleted (
QE-Core: Ready)
Updated by punkioudi about 3 years ago
Consecutive runs with git-refspec :
https://openqa.suse.de/tests/5921013
https://openqa.suse.de/tests/5921104
https://openqa.suse.de/tests/5921163
Issue still cannot be reproduced.
Updated by punkioudi almost 3 years ago
- Status changed from In Progress to Resolved