action #121654
closedNeed ensure grub_test_snapshot to select read-only snapshot in grub
0%
Description
Motivation¶
This issue happened on ppc64le randomly and somehow related with the previous 'bonce back' issue, https://openqa.nue.suse.com/tests/10091621#step/grub_test_snapshot/20 It failed since system just boot on local disk directly and no bonce back to bootloader , then won't enter grub menu so can't select read-only snapshot for test.
Successful job: https://openqa.nue.suse.com/tests/10092056#step/grub_test_snapshot/9 for comparison.
Acceptance criteria¶
AC1: Make sure the test to select read-only snapshot in grub
Suggestions¶
- We may need change/update the code logic for 'bonce back' on ppc64le.
Updated by leli over 1 year ago
- Related to action #119581: Track: how to distinguish these tags(bootloader, grub, inst-bootmenu) in needles added
Updated by JERiveraMoya over 1 year ago
this is another case where we start to invest too much time in fixing tests with unsupported virtualization.
we might need to run the whole test suite in PowerVM but as this test suite is a migration goes from one product to another we might need to experiment with that in the future (running SLE 12 in PowerVM I mean).
For now I don't think it is a requirement to do anything related with snaphshots after migration, more like an extra.
Let's remove that part to make this test stable still using Power KVM: #122206
Updated by JERiveraMoya over 1 year ago
- Related to action #122206: Avoid booting from snapshot in PowerKVM for migrations added
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: ha_migration_offline_sles12sp4_ltss_pscc_def_full@ppc64le
https://openqa.suse.de/tests/10219956#step/grub_test_snapshot/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 about 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: offline_sles12sp5_media_sdk-lp_all_full@ppc64le
https://openqa.suse.de/tests/10436153#step/grub_test_snapshot/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.
Updated by JERiveraMoya about 1 year ago
- Status changed from New to Rejected
doesn't happen at least at that test suite, we have other ticket for that somewhere seen in another test suite.