action #37048
closed[sle][functional][y] test YaST first boot scenario on different architectures
0%
Description
Motivation¶
We don't cover first boot configuration in automated tests, which brings risks of breaking existing functionality (e.g. https://bugzilla.suse.com/show_bug.cgi?id=1095253)
See YaST documentation.
Acceptance criteria¶
AC1: test suite which verifies basic functionality is added
AC2: AY profile which verifies feature is added
Suggestions¶
Functionality can be enabled with following settings in the profile:
<firstboot>
<firstboot_enabled config:type="boolean">true</firstboot_enabled>
</firstboot>
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional] test YaST first boot scanario on different architectures to [sle][functional][y] test YaST first boot scenario on different architectures
- Target version set to Milestone 20
Not sure how the "first boot module" is related to the reported bug though.
Updated by teclator almost 6 years ago
okurz wrote:
Not sure how the "first boot module" is related to the reported bug though.
Well, the RPi3 image uses firsboot by default with its own control file.
The bug reported was a specific issue trying to go back from the last step (already fixed)
Updated by okurz almost 6 years ago
- Target version changed from Milestone 20 to Milestone 20
Updated by okurz over 5 years ago
- Target version changed from Milestone 20 to Milestone 21
Updated by okurz over 5 years ago
- Status changed from New to In Progress
- Assignee set to okurz
Updated by okurz over 5 years ago
- Status changed from In Progress to Feedback
Tried manually, I can't seem to trigger the first boot wizard properly, trying with the help of openQA:
openqa_clone_job_osd --skip-chained-deps 2272249 TEST=autoyast_firstboot_wizard_poo#37048 AUTOYAST=http://w3.suse.de/~okurz/autoyast_firstboot.xml AUTOYAST_CONFIRM= _GROUP="Test Development: SLE 15"
Created job #2275135: sle-15-SP1-Installer-DVD-x86_64-Build100.4-autoyast_mini@64bit -> https://openqa.suse.de/t2275135
failed because remote templates are not "prepared" -> #44243
openqa_clone_job_osd --skip-chained-deps 2272249 TEST=autoyast_firstboot_wizard_poo#37048 AUTOYAST=http://w3.suse.de/~okurz/autoyast_firstboot_expanded.xml AUTOYAST_PREPARE_PROFILE= AUTOYAST_CONFIRM= _GROUP="Test Development: SLE 15"
Created job #2275174: sle-15-SP1-Installer-DVD-x86_64-Build100.4-autoyast_mini@64bit -> https://openqa.suse.de/t2275174
Created bug https://bugzilla.suse.com/show_bug.cgi?id=1117068
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6274
Updated by okurz over 5 years ago
- Status changed from Feedback to Workable
- Assignee deleted (
okurz)
PR merged, the profile is in the tests new, we should add a new scenario, can we handle that in this sprint?
Updated by riafarov over 5 years ago
- Status changed from Workable to Blocked
https://bugzilla.suse.com/show_bug.cgi?id=1117068 agreed to wait for bug fix before enabling test.
Updated by okurz over 5 years ago
- Due date deleted (
2018-12-18) - Assignee set to okurz
- Target version changed from Milestone 21 to Milestone 22
blocked by bug, we might require test changes after bug resolution
Updated by okurz over 5 years ago
bug is RESOLVED FIXED, waiting for https://build.opensuse.org/request/show/653568 and https://build.opensuse.org/request/show/653575 and https://build.opensuse.org/request/show/655870 and https://build.suse.de/request/show/179012 and https://build.suse.de/request/show/179009 and https://build.suse.de/request/show/178770
Updated by okurz about 5 years ago
- Status changed from Blocked to Workable
- Assignee deleted (
okurz) - Target version changed from Milestone 22 to Milestone 24
All SRs are in. We can now test on openQA with the profile that is already in os-autoinst-distri-opensuse: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6274
Updated by riafarov almost 5 years ago
- Status changed from Workable to Rejected
- Assignee set to riafarov
Handled in #49508