action #66114
Updated by SLindoMansilla almost 4 years ago
## 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:
```yaml
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 Tasks
- **AC:** bootloader_start is the only test module scheduled for handling bootloader in functional job group
## Tasks
1. Adapt **bootloader_start** to work in with all scenarios (arch, backend, etc) used arch/backend from QSF-U job group.
2. - Replace the conditional schedule with **bootloader_start**.