Feature 317701: Additional bootloader testing: Do not use perl-bootloader in yast2-bootloader
|Target version:||openQA Project - Milestone 3|
For details see https://fate.suse.com/317701
First check if the Feature status is "done".
In past perl-Bootloader is used as abstraction layer over various bootloaders and also as a way how to not write code in ycp for bootloader.
Now situation is completelly different. Yast code is in ruby. We support only single bootloader. And last but not least GRUB2 configuration is just writting some values to inifile like files and run some scripts.
In such situation perl-Bootloader just adds additional source of problems with no clear benefits.
So proposal is to write config files and run scripts directly in yast2-bootloader and keep perl-Bootloader only as thin layer for updating kernel to ensure menu is regenerated after new kernel installation.
#5 Updated by okurz over 3 years ago
- Status changed from New to In Progress
Fails in migration scenarios, e.g. https://openqa.suse.de/tests/488075#step/no_perl_bootloader/3
For clean installation it works: https://openqa.suse.de/tests/487875#step/no_perl_bootloader/1
Fix for upgrade: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1578
#6 Updated by okurz over 3 years ago
There is also AUTOUPGRADE…: https://openqa.suse.de/tests/493101 fixed by https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1606
#9 Updated by okurz over 3 years ago
- Status changed from Feedback to Resolved
Feature test: PASSED
working example: https://openqa.suse.de/tests/502456#step/no_perl_bootloader/1