action #113734
Updated by JERiveraMoya over 2 years ago
#### Motivation ##### In theory it should be possible to add those many repositories for the Maintenance Updates using a Driver Update Disk. In Product validation we have an example of the creation of this DUD by one job and its use by another job: [generate_dud](https://openqa.suse.de/tests/8751659) [dud_development_tools](https://openqa.suse.de/tests/8753153) 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. #### Scope #### SLE-15-SP{3,4}, where we can use libyui REST. #### 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 **AC2**: An equivalent test module to [installation/dud_addon](https://openqa.suse.de/tests/8753153#step/dud_addon/1) 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. Note: there is a problem after install, the screenshot is attached. **** draft ****