action #37048
closed
[sle][functional][y] test YaST first boot scenario on different architectures
Added by riafarov almost 6 years ago.
Updated about 5 years ago.
Target version:
SUSE QA - Milestone 24
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>
- 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.
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)
- Target version changed from Milestone 20 to Milestone 20
- Target version changed from Milestone 20 to Milestone 21
- Status changed from New to In Progress
- Assignee set to okurz
- 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
- Due date set to 2018-12-18
- 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?
- Status changed from Workable to Blocked
- 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
- Status changed from Blocked to Workable
- Assignee deleted (
okurz)
- Target version changed from Milestone 22 to Milestone 24
- Status changed from Workable to Rejected
- Assignee set to riafarov
Also available in: Atom
PDF