action #157474
opencoordination #151816: [epic] Handle openQA fixes and job group setup
Remove package Hub from SLE 12 SP5 migrations and resolve vendor changes for SLE 15 SP5
0%
Description
According to the response in a dependency issue bug report: https://bugzilla.suse.com/show_bug.cgi?id=1209498#c3
We should remove packagehub from migration scenarions as it is not L3 supported.
In the PRD is explicitly mentioned about not supported for SLE 12 SP5, for SLE 15 SPN is on best effort.
Latest conflict issues for two migration tests that include phub prior migration: https://openqa.suse.de/tests/13793854#step/resolve_dependency_issues/28 and https://openqa.suse.de/tests/13793867#step/resolve_dependency_issues/3
Additionally we have a mechanism to resolve vendor changes for the SLE 15 SP5 failures related with phub.
Acceptance criteria¶
AC1: phum module removed from SLE 12 SP5 migrations.
AC2: Vendor changes for SLE 15 SP5 addressed via setting that activate that testing path in the UI.
Updated by JERiveraMoya about 1 month ago
- Tags set to qe-yam-mar-sprint
- Subject changed from Remove package Hub from migration tests to Remove package Hub from SLE 12 SP5 migrations and resolve vendor changes for SLE 15 SP5
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to zoecao
- Parent task set to #151816
Updated by zoecao about 1 month ago ยท Edited
I already cloned the jobs with phub by adding VENDOR_CHG_DEPS=1 (used for resolve vendor change issue) in milestone group:
https://openqa.suse.de/tests/13839389
https://openqa.suse.de/tests/13839257 (besides vendor change issue, it also has a dependency issue, so mark the related bug)
The setting works fine in above jobs.
But need to add the related code to yast2 migration by submitting PR for the case below:
https://openqa.suse.de/tests/13845153#step/yast2_migration/13
I'm working on it.
Updated by zoecao about 1 month ago
Submit MR to remove SLES12SP5+phub testsuite, and set vendor change by adding setting for SLES15SPx testsuites.
https://gitlab.suse.de/qe-yam/openqa-job-groups/-/merge_requests/123
But the setting doesn't work on the yast2 migration case, I file a new ticket on it, it seams we haven't implemented it on yast2 migration cases: https://progress.opensuse.org/issues/157729
Updated by openqa_review 11 days 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: migr_sles12sp5_phub
https://openqa.suse.de/tests/13818526#step/resolve_dependency_issues/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.