action #122335
closed
sap_migration_offline_common_x86_64 cannot not start due wrong settings
Added by shukui almost 2 years ago.
Updated over 1 year ago.
Description
Motivation¶
openQA test in scenario sle-15-SP5-Migration-from-SLE15-SPx-x86_64-sap_migration_offline_common_x86_64@64bit-2gbram-cirrus fails in
version_switch_origin_system
We should fix settings for this scenario to start.
Acceptance¶
AC1: Fix settings so the scenario can run
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sap_migration_offline_common_x86_64@64bit-2gbram-cirrus
https://openqa.suse.de/tests/10221244#step/version_switch_origin_system/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.
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sap_migration_offline_common_x86_64@64bit-2gbram-cirrus
https://openqa.suse.de/tests/10352427#step/version_switch_origin_system/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.
- Subject changed from sap_migration_offline_common_x86_64 should not start to sap_migration_offline_common_x86_64 cannot not start due wrong settings
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Current
- Assignee set to tinawang123
- Status changed from Workable to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF