Project

General

Profile

Actions

action #115277

closed

Apply self_update always in interactive installation in MUs aggregates

Added by JERiveraMoya about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-08-12
Due date:
% Done:

100%

Estimated time:

Description

Motivation

In Maintenance testing for aggregate we are testing the interactive installation in some test suite without having in bootloader parameters self_update pointing to a proper maintenance repo. This means that the installer is updated by default and takes the latest package from scc.
For example in this case https://openqa.suse.de/tests/9318039#step/bootloader_start/9
will pull from official channels: https://updates.suse.com/SUSE/Updates/SLE-INSTALLER/15-SP4/x86_64/update/
This mean that we are not testing the latest updates for the installer, so the installer is the same, the screen are the same, the packages that tune your system are the same, there is not need for testing it over and over, it is static.
Once we set the parameter like in here: https://openqa.suse.de/tests/9318044#step/bootloader_start/9 we also will pull the latest from scc plus new updates for the installer itself, so then it make sense to test for example partitioning.
In summary, these scenarios inherited from Core squad missed this logic, there is no point on testing partitioning for every single build (which happen daily) during interactive installation which is using yast-storage-ng if we don't pass that parameters, as we would be testing always the version in scc, or in other words already approved updates.

For quarter updates seems that is option is disabled by default not even connecting to scc to update the installer, makes sense because there GM images are not used, those new images already have newer packages. We are still not there, we don't have yet single-incidents or quarter update maintenance testing, once we have stability with libyui-rest-api in aggregate we plan to tackle those as well.

Acceptance criteria

AC1: All the interactive installation in YaST MUs job group have set self_update as bootloader parameter

Actions #1

Updated by JERiveraMoya about 2 years ago

  • Subject changed from Apply self_update always in interactive installation in MUs to Apply self_update always in interactive installation in MUs aggregates
Actions #2

Updated by JERiveraMoya about 2 years ago

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

Updated by hjluo about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #4

Updated by hjluo about 2 years ago

VR for 15:sle-15-Server-DVD-Updates-x86_64 -autoyast_filesystem_withouthome_yast
https://openqa.nue.suse.com/tests/9392116#step/bootloader/8

Actions #5

Updated by JERiveraMoya about 2 years ago

we will need extensive verification of all the jobs in https://openqa.suse.de/group_overview/421 which runs an interactive installation.
You pasted only one example of AutoYaST and made me think as well if we need it, it is using as well the UI https://openqa.suse.de/tests/9390280#step/installation/3 although there is no interaction, my guess is that the autoinstallation also will be updated via that setting, so if you could also include that settings in AutoYaST jobs.

Actions #7

Updated by hjluo about 2 years ago

  • % Done changed from 0 to 100

MR merged.

Actions #8

Updated by hjluo about 2 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF