Actions
action #66114
closed[functional][u] Use bootloader_start instead of arch/backend specific test module
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Refactor/Code Improvements
Target version:
SUSE QA - Milestone 30
Start date:
2020-04-27
Due date:
% Done:
0%
Estimated time:
42.00 h
Difficulty:
Description
Motivation¶
At the moment there are different arch/backend specific bootloader modules
- bootloader
- bootloader_hyperv
- bootloader_s390
- bootloader_svirt
- bootloader_uefi
- bootloader_zkvm
They cause to repeat the following conditional schedule:
conditional_schedule:
bootloader:
ARCH:
'aarch64':
- boot/uefi_bootmenu
's390x':
- installation/bootloader_zkvm
MACHINE:
'svirt-xen-pv':
- installation/bootloader_svirt
'svirt-xen-hvm':
- installation/bootloader_svirt
There is a module that should implement all those arch/backend specific behavior:
- bootloader_start
Acceptance criteria¶
- AC: bootloader_start is the only test module scheduled for handling bootloader in functional job group
Tasks¶
- Adapt bootloader_start to work in all scenarios (arch, backend, etc) from QSF-U job group.
- Replace the conditional schedule with bootloader_start.
Actions