Bug ID | 1018280 |
---|---|
Summary | yast bootloader fails on AArch64 if grub2 not installed or grub.cfg unavailable |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | aarch64 |
OS | SUSE Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | YaST2 |
Assignee | yast2-maintainers@suse.de |
Reporter | afaerber@suse.com |
QA Contact | jsrain@suse.com |
CC | agraf@suse.com, dmueller@suse.com, mbrugger@suse.com, yousaf.kaukab@suse.com |
Found By | --- |
Blocker | --- |
Observed: 1) Using a JeOS rootfs tarball with a TFTP-booted kernel on an AArch64 board results in a fatal error dialog, complaining about not being able to read /etc/default/grub. This can be worked around by installing grub2-arm64-efi. 2) After grub2 is installed it will show a fatal error dialog complaining that /boot/grub2/grub.cfg cannot be read. This can be worked around by grub2-mkconfig -o /boot/grub2/grub.cfg. 3) With grub2 installed and grub.cfg in place, it will start up normally. Expected: a) Absence of grub2 packages should be ignored. When selecting grub2 in the YaST UI install, the necessary packages should be installed, as done for others. b) If grub.cfg doesn't exist yet, it should be generated.