action #153415
closedcoordination #151816: [epic] Handle openQA fixes and job group setup
Add python3 module in register_extensions_and_modules
0%
Description
Motivation¶
Related job: https://openqa.suse.de/tests/13228695#step/register_extensions_and_modules/1
python3 is not be selected
But python3 is default module for sles15sp5
We need to add register 'python3' at installation/module_registration/register_extensions_and_modules
Acceptance criteria¶
AC1: Add python3 module in register_extensions_and_modules
Updated by JERiveraMoya 9 months ago
- Tags set to qe-yam-feb-sprint
- Subject changed from Need add python3 module for register_extensions_and_modules to Add python3 module in register_extensions_and_modules
- Description updated (diff)
- Status changed from New to Workable
- Parent task set to #151816
Updated by lmanfredi 9 months ago ยท Edited
In the last build 20240123-1, the issue happens: the Python3 module is not selected for 15-SP5
Updated by JERiveraMoya 8 months ago
- Tags changed from qe-yam-feb-sprint to qe-yam-jan-sprint
Updated by JERiveraMoya 8 months ago
This test module relies on a fixed list of scc addons.
Option 1: create something like ensure_activated_link in lib/YuiRestClient/Widget/RichText.pm ... doesn't feel right, then we would be checking for the other test modules/extension where we only need one click if it is already selected, not bad, but not QE straightforward code IMO for the reader.
Option 2: Do not add stuff that is default, same like we do for basesystem or server, we don't care about them. If we add a validation in the future we could provide with test data and not with the openQA setting.
As we CANNOT change it at the level of medium, where this setting is coming from, because this is used for other squad, we need to override in job group yaml only for us.
I would prefer option 2.
Updated by JERiveraMoya 8 months ago
- Tags changed from qe-yam-jan-sprint to qe-yam-feb-sprint
Updated by JERiveraMoya 8 months ago
- Status changed from In Progress to Resolved