Project

General

Profile

Actions
Copy link

action #129649

closed

coordination #130072: [epic] Handle openQA adaptions in Yam squad - SLE 15 SP6

Need deal with the scenario when no bonce back happened on powerkvm

Added by leli over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
leli
Target version:
Current
Start date:
2023-05-22
Due date:
% Done:

0%

Estimated time:

Description

Motivation

We have workaround the situation when no bonce back happened on powerkvm, but it is not work when online_migration_setup loaded after bootloader module.
Because when showed 'display manager' but test still used wait_boot -> boot_local_disk which will match from the point of bootloader. We need ensure if no bonce back happend it won't go back to grub2 for the test process, and go ahead, that handle_grub shouldn't be called anymore after dispaly-mananger selected in bootloader module.

online_migration_setup

Acceptance criteria

AC1: Need deal with the scenario make test process go correct process when no bonce back happened on powerkvm

Actions
Copy link
 #1

Updated by leli over 1 year ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by leli over 1 year ago

  • Status changed from New to Workable
  • Target version set to Current
Actions
Copy link
 #3

Updated by leli over 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to leli
Actions
Copy link
 #4

Updated by leli over 1 year ago

  • Description updated (diff)
Actions
Copy link
 #6

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: online_sle12sp5_sles15sp4_sles15sp5_pscc_all_full_y_
https://openqa.suse.de/tests/11164842#step/online_migration_setup/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions
Copy link
 #8

Updated by JERiveraMoya over 1 year ago

  • Status changed from In Progress to Resolved
  • Parent task set to #130072
Actions
Copy link
 #9

Updated by openqa_review over 1 year ago

  • Status changed from Resolved to Feedback

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: online_sle12sp5_sles15sp4_sles15sp5_pscc_all_full_y_
https://openqa.suse.de/tests/11164842#step/online_migration_setup/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 32 days if nothing changes in this ticket.

Actions
Copy link
 #10

Updated by JERiveraMoya over 1 year ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF