Project

General

Profile

Actions
Copy link

action #124916

closed

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

Resolve conflicts for SMT cases in migration milestone group

Added by zoecao almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
rainerkoenig
Target version:
-
Start date:
2023-02-22
Due date:
% Done:

0%

Estimated time:

Description

Motivation:
For the SMT cases, when doing migration, all of the available modules of the target product will be added, see the [screenshot here], Packagehub is included in the module list. Because the packages in Packagehub are openSUSE packages, so when doing upgrade, there would be a warning about "Vendor change", some packages' vendor is changed from SUSE to openSUSE which is reasonable, so need to resolve it.
Failure: https://openqa.suse.de/tests/10555161#step/yast2_migration/14

Actions
Copy link
 #1

Updated by JERiveraMoya almost 2 years ago

  • Status changed from New to Workable
  • Target version set to Current

can we add the screenshot with what is supposed to resolve?
do we have another case like this? but makes sense due to the vendor change.

Actions
Copy link
 #2

Updated by JERiveraMoya almost 2 years ago

  • Target version deleted (Current)
  • Parent task set to #121876
Actions
Copy link
 #3

Updated by zoecao almost 2 years ago

In the current milestone job group, only this case has this issue, some SMT cases are using 'zypper' to do migration, command "zypper migration --allow-vendor-change" could resolve the vendor change issue; And another two smt cases using "yast" method failed earlier.

I found the [ticket]: Update cases to use RMT server instead of SMT server to do register at milestone job group, if we don't use SMT, then no need to resolve the vendor change issue, wdyt?

Actions
Copy link
 #4

Updated by rainerkoenig almost 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to rainerkoenig
Actions
Copy link
 #5

Updated by rainerkoenig almost 2 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #6

Updated by openqa_review almost 2 years 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_sles15sp3_smt_basesys-srv-live-tsm_def_full_y
https://openqa.suse.de/tests/10555161#step/yast2_migration/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
 #7

Updated by rainerkoenig over 1 year ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF