Project

General

Profile

Actions

action #122206

closed

coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5

Avoid booting from snapshot in PowerKVM for migrations

Added by JERiveraMoya over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Target version:
Start date:
2022-12-20
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Failures related with the 'bounce back' keep making test suites for migration running in Power KVM quite unstable, i.e.:
https://openqa.nue.suse.com/tests/10091621#step/grub_test_snapshot/20

Yam squad tried previously some mitigations, but it is still happening. This is another case where it should be avoided to invest too much time in fixing tests with unsupported virtualization.
One option could be to run the test suite in PowerVM but as this test suite is a migration goes from one product to another it would be required some experimentation with that in the future (running SLE 12 in PowerVM I mean).
For now as it is not a requirement for migration 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.

Acceptance criteria

AC1: Unschedule test modules related with booting previous snapshot to come back to the system before migration

Additional information

Only apply where in the history, migration failures has been seen for Power KVM


Related issues 1 (0 open1 closed)

Related to qe-yam - action #121654: Need ensure grub_test_snapshot to select read-only snapshot in grubRejected2022-12-07

Actions
Actions #1

Updated by JERiveraMoya over 1 year ago

  • Related to action #121654: Need ensure grub_test_snapshot to select read-only snapshot in grub added
Actions #2

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #3

Updated by syrianidou_sofia over 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia
Actions #4

Updated by syrianidou_sofia about 1 year ago

  • Status changed from In Progress to Feedback
Actions #5

Updated by syrianidou_sofia about 1 year ago

  • Status changed from Feedback to Blocked
Actions #6

Updated by JERiveraMoya about 1 year ago

We don't use blocked either, please use just 3 states, at the end this blocks are just internal blocks. We should try some solution at least if nobody can help or guide you with that.
We only used block state in the past for bugs and in those cases, we can just move to backlog again.

Actions #7

Updated by JERiveraMoya about 1 year ago

  • Status changed from Blocked to In Progress
Actions #8

Updated by syrianidou_sofia about 1 year ago

  • Status changed from In Progress to Feedback

The ppc tests that have history of failure are mainly in migration daily. One test was found in migration milestone job group. I have changed the setting of each test ROLLBACK_AFTER_MIGRATION which should remove from their schedule 3 modules :grub_test_snapshot, version_switch_origin_system#1 and snapper_rollback

https://gitlab.suse.de/coolgw/wegao-test/-/merge_requests/206

Actions #9

Updated by JERiveraMoya about 1 year ago

  • Status changed from Feedback to In Progress

putting back to in-progress, we don't use feedback state since a lot of time ago because most of the ticket went from in-progress to feedback and stay there even there was substantial progress or the opposite, they went to feedback and accumulate there, basically that status doesn't tell us anything when it is due to internal dependency, review, etc. It was used for bugs blocking us, but in those case we prefer to move the ticket to backlog in new and re-refine it.

Actions #10

Updated by JERiveraMoya about 1 year ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF