action #111743
closedcoordination #109187: [Epic] Add AutoYaST test suites for dependencies in YaST Maintenance Updates and keep interactive installations
Add AutoYaST test suites for chained dependencies in YaST Maintenance Updates (rest of products)
Description
Motivation¶
See #109187
It is done for SLE-15-SP{3,4} in #109214. Let's try to reuse the same AutoYaST profile for the rest of the products in maintenance.
mru-install-desktop-with-addons | mru-install-minimal-with-addons
Previous experience indicated that any minimal failure/mistake setting this basically cascade to all job group, for that reason it is better to do in Development job group. Then we will file another ticket to deploy this in YaST MU job group.
Scope¶
Test suites with external dependencies: mru-install-desktop-with-addons & mru-install-minimal-with-addons
Products: rest of the products in maintenance.
Architectures: for the minimal is running in three architectures, aim for all of them if possible.
Acceptance criteria¶
AC1: New AutoYaST test suites are created in 'YaST Maintenance Updates - Development' openQA job group corresponding to mru-install-desktop-with-addons & mru-install-minimal-with-addons.
AC2: Copies of the chained dependencies of test suites mru-install-desktop-with-addons & mru-install-minimal-with-addons which are in YaST MU job group will be set to new AutoYaST test suites in 'YaST Maintenance Updates - Development' job group
AC3: If we cannot reuse the AutoYaST profile created for SLE-15-SP{3,4} consider to reduce the scope of products or architectures to migrate to AutoYaST.
Suggestions¶
- Reuse knowledge from previous task: #107674 #109187
- We could reuse very likely the AutoYaST profiles created for SLE-15-SP3.
- We should rename all test suite creating AutoYaST image to
autoyast_create_*
so we can distinguish better between old and new things regardless of the job group, maintenance or product as it might be confusing.
Updated by JERiveraMoya over 2 years ago
- Subject changed from Add AutoYaST test suites for chained dependencies in YaST Maintenance Updates in SLE-15-SP3 to Add AutoYaST test suites for chained dependencies in YaST Maintenance Updates (rest of products)
Updated by JERiveraMoya over 2 years ago
- Related to action #112352: Move mru-iscsi_(client|server)_normal_auth_backstore_(fileio|hdd|lvm) to YaST MU added
Updated by JERiveraMoya over 2 years ago
- Tags deleted (
qe-yast-refinement) - Status changed from New to Workable
Updated by JERiveraMoya over 2 years ago
- Tags set to qe-yast-refinement
- Status changed from Workable to New
Updated by JERiveraMoya over 2 years ago
- Tags deleted (
qe-yast-refinement) - Status changed from New to Workable
Updated by geor over 2 years ago
- Status changed from Workable to In Progress
- Assignee set to geor
Updated by livdywan about 2 years ago
This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by JERiveraMoya about 2 years ago
Should split this ticket somehow to move forward? perhaps you have some draft already or PR that I missed.
Updated by geor about 2 years ago
JERiveraMoya wrote:
Should split this ticket somehow to move forward? perhaps you have some draft already or PR that I missed.
Yes this is taking me too long, jumping on it on and off, maybe I can just finalize SLE 15, SLE 15-SP1 and SLE 15-SP2, all archs. The leftover would be 12-SP4 and 12-SP5 all archs, if we end up deleting our LTSS job groups.
Updated by JERiveraMoya about 2 years ago
yes, no worries, we should have split a bit more.
please create ticket with the part you mentioned.
thanks!
Updated by JERiveraMoya about 2 years ago
Updated by geor about 2 years ago
JERiveraMoya wrote:
is there any MR with the setup?
Good point I have omitted it:
https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/398
Updated by geor about 2 years ago
- Status changed from In Progress to Resolved
All testsuites are running ok in production for some time now, with the exception of the iscsi multimachine jobs (which are failing in development group).
related followup ticket created: https://progress.opensuse.org/issues/118966