action #154024
closed
coordination #151816: [epic] Handle openQA fixes and job group setup
Provide installation with skip_registration in maintenance updates
Added by JERiveraMoya 11 months ago.
Updated 11 months ago.
Description
Motivation¶
We don't have an scenario that covers https://bugzilla.suse.com/show_bug.cgi?id=1218977 because it is a corner case, it would tell more the installer than those unapproved maintenance updates, but actually it would test that the installer can handle an installation skipping the registration and self-updating itself with a test channel that contains unapproved maintenance updates, so it make sense.
We should reuse test modules in product validation to create a test suite with libyui-rest-api test modules, https://openqa.suse.de/tests/13084480#step/skip_registration/1
Scope¶
All products in maintenance.
Acceptance criteria¶
AC1: Add scenario that skip registration to maintenance updates aggregates.
In order to detect this bug we don't need to add the unapproved maintenance updates as addons, because it can be seen before that, just after skipping registration, but I'm asking if this scenario would make sense to add them or not because the system would be in GM and it might be too old to apply the unapproved updates directly in the installer.
note: btw, I checked manually and it is easy to reproduce, just boot the Full medium and add regurl and self_update and skip registration.
- Tracker changed from coordination to action
- Status changed from Workable to In Progress
- Assignee set to syrianidou_sofia
The latest build 20240123-1 is still using the outdated yast2-pkg-bindings packages and the tests break after the skip_registration point. We have added the skip_registration tests into production but need to force soft fail as for 15SP3 and 15Sp5 are expected to fail due to bug#1218977 if the fix will not be included in the next build as well.
Also, prepared MR: https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/709 to add the self update repo once the fix is included.
- Status changed from In Progress to Resolved
We can resolve this ticket, now we have this test suite there to be safe and some peace of mind, now only we need to keep working providing info to the bug(s).
Also available in: Atom
PDF