action #112118

coordination #112115: [Epic] Finalize split of Core Maintenance Updates adding remaining test suites to YaST Maintenance Updates

Handle create_hdd_minimal_base+sdk+python2 in YaST Maintenance Updates

Added by JERiveraMoya 10 months ago. Updated 8 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



See parent ticket #112115
Installing product modules 'development and 'python2' is covered already as part of the existing AutoYaST creation image create_hdd_yast_maintenance_minimal in YaST MU.
For the same reason, Core MU already covers this in mru-install-minimal-with-addons (until they will move this one to its own AutoYaST like in create_hdd_yast_maintenance_minimal).
In Kernel MU run 4 chained jobs which can be re-linked to mru-install-minimal-with-addons in Core (until Kernel squad will move to have their own AutoYaST image).

The plan for this test suite is to remove this test suite in Core MU and configure the parent switching.
In the future Kernel will migrate to AutoYaST.

AC1: Remove test suite 'create_hdd_minimal_base+sdk+python2' in Core Maintenance Update job group.
AC2: Reconfigure chained dependencies with jobs in Kernel MU to point to mru-install-minimal-with-addons in Core MU.


Test those Kernel job chained jobs with the new parent to avoid surprises (but the fact that we register a few more modules, like legacy, containers, etc. without actually including their patterns should not have any effect in theory).


#1 Updated by JERiveraMoya 10 months ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable

#2 Updated by JRivrain 10 months ago

  • Assignee set to JRivrain

#3 Updated by JRivrain 10 months ago

  • Status changed from Workable to In Progress

#5 Updated by JRivrain 10 months ago

  • Status changed from In Progress to Feedback

#6 Updated by okurz 8 months ago

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on First reminder: Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days).

#7 Updated by JERiveraMoya 8 months ago

  • Status changed from Feedback to In Progress

#8 Updated by JRivrain 8 months ago

  • Status changed from In Progress to Closed

This was merged 1 month ago, left opened by error (not closed before vacation...)

Also available in: Atom PDF