[functional][u] Use bootloader_start instead of arch/backend specific test module
At the moment there are different arch/backend specific bootloader modules
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:
- AC: bootloader_start is the only test module scheduled for handling bootloader in functional job group
- Adapt bootloader_start to work in all scenarios (arch, backend, etc) from QSF-U job group.
- Replace the conditional schedule with bootloader_start.
#4 Updated by SLindoMansilla over 1 year ago
I checked bootloader_start.pm only question is about xen pv regarding the bsc#961638. So this is not clear to me atm.
I haven't looked at the code but, the bug is mentioning that the boot menu is not shown via VNC, which I would consider expected since there is no display manager started at that point. The boot menu needs to be handled via serial console. Am I missing something?
#10 Updated by dheidler about 1 year ago
- Status changed from Feedback to Resolved