action #138179
closed
coordination #121864: [epic] Split and enhance test modules in migrations
Adapt the addon selection in migration cases for ltss and python2 module removement
Added by zoecao 7 months ago.
Updated 5 months ago.
Description
Motivation
This ticket is related with split patch_sle. The ltss and python2 module are dropped before migration, need to adjust the SCC_ADDONS to make it wont't tend to find the ltss and python2 module when selecting modules during migration.
The failure job link: https://openqa.suse.de/tests/12051316#
And related ticket: https://progress.opensuse.org/issues/132920 of the following part：
Finally after each the two modules create above we might need to adjust the settings, but I don't think it is responsibility of this module to do this, during the migration itself ltss or python can be excluded. File a ticket to adjust it there if it is not possible at the moment and keep this code or even better fix it there on target.
@all_addons = grep { $_ ne $name } @all_addons;
set_var('SCC_ADDONS', join(',', @all_addons));
Acceptance criteria
AC1: Adjust the SCC_ADDONS to make it wont't tend to find the ltss and python2 module when selecting modules during migration.
The idea should be adjust the SCC_ADDONS to remove dropped modules such as ltss,python2, etc. modules for migration test. Any dropped modules should be removed from SCC_ADDONS after patching since it won't be supported on target system.
- Status changed from New to Workable
- Target version set to Current
- Parent task set to #121864
- Priority changed from Normal to High
- Status changed from Workable to In Progress
- Assignee set to lmanfredi
The fix should be done in the file JobGroups/migration_development.yaml by removing from the SCC_ADDONS list the values: python2,ltss for the test suites with names ending with _split_patch_sle.
But I would like to have a confirm of that. Also because looking the related (resolved) ticket, I can see that there is a MR, already merged, that does the reverse of what I would like to do.
Moreover, looking the current tests in the job group 319, I can see that we have some issues in these test cases (*_split_patch_sle) that happens in a previous module respect to the module installation/addon_products_sle.pm related to this ticket. So, how can I test my fix?
- Status changed from In Progress to Blocked
- Status changed from Blocked to In Progress
Created openqa-job-groups-migrations MR#384
Created os-autoinst-distri-opensuse PR#18194
Merged os-autoinst-distri-opensuse PR#18194
Merged openqa-job-groups-migrations MR#384
- Status changed from In Progress to Resolved
Also available in: Atom
PDF