Project

General

Profile

action #113734

coordination #112571: [Epic] Enable libyui REST in YaST MU

Add maintenance updates as additional add-on products via Driver Update

Added by JERiveraMoya 7 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-07-18
Due date:
% Done:

0%

Estimated time:

Description

Motivation

It is possible to add those many repositories for the Maintenance Updates using a Driver Update Disk (DUD). In Product validation we have an example of the creation of this DUD by one job and its use by another job:
generate_dud
dud_development_tools

When tested manually with SLE-15-SP4 all those updates were visible in one popup and can be added to the installation, also those repos are visible when inspecting Software -> Details -> repositories in Installation Settings. Installation is able to finish.
Another motivation is the 40 minutes required to add one by one with needles, which can be drastically reduced, perhaps to ~ 5 minutes.

The way we test those maintenance updates using so many repositories is a bit strange, but I guess it has its advantage, so we might use this also no-so-conventional approach to testing. Nevertheless we should have as well the option to add the repos iteratively during installation (see #113731), in case we would want to fall back to this solution for some reason, some bug in the dud mechanism, or perhaps because of its insecure nature. But anyway we are in a testing environment and it might be very useful as you can see.

Scope

SLE-15-SP{3,4}, where we can use libyui REST, but we can start applying only to one test suite for example.

Acceptance criteria

AC1: New test suite creating DUD is added to YaST MUs - Dev
AC2: Test suite for creation is chained to test suite of your choice using full libyui REST
AC3: An equivalent test module to installation/dud_addon using libyui REST API is created.

Suggestions

A test suite of your choice means that we can use any of the test suites adding those repos and replacing their modules by equivalent libyui REST ones, and of course all should happen in openQA job group YaST MUs - Dev.

Troubleshooting: there is a problem after install, some kernel error faced during manual testing in the first boot after install. It was solved just adding all the product modules. It might happen that if there are updates added as repos and not the product module relative to those update, even if the installation can be performed something might get in some inconsistent state.

add_on_products.xml (58 KB) add_on_products.xml example of .xml to include in the DUD containing maintenance updatesdates JERiveraMoya, 2022-07-20 05:37

History

#1 Updated by JERiveraMoya 7 months ago

  • Description updated (diff)

#2 Updated by JERiveraMoya 7 months ago

  • Description updated (diff)

#3 Updated by JERiveraMoya 7 months ago

  • Description updated (diff)

#5 Updated by JERiveraMoya 7 months ago

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

#6 Updated by tinawang123 6 months ago

  • Assignee set to tinawang123

#7 Updated by tinawang123 6 months ago

  • Status changed from Workable to In Progress

#10 Updated by tinawang123 6 months ago

  • Status changed from In Progress to Resolved

#11 Updated by JERiveraMoya 6 months ago

  • Status changed from Resolved to In Progress

we are not installing the maintenance updates via this method, just one add-on for dev-tools.
We need to generate the xml with all the updates to create a dud with all of them.
Let's revisit together the goal of this ticket.

#12 Updated by tinawang123 6 months ago

I think it already used xml file
Please check this screen: https://openqa.suse.de/tests/9332343#step/generate_dud/17

#15 Updated by tinawang123 5 months ago

  • Status changed from In Progress to Resolved

#16 Updated by JERiveraMoya 5 months ago

  • Status changed from Resolved to In Progress

#19 Updated by tinawang123 5 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF