Mailinglist Archive: opensuse-bugs (4250 mails)

< Previous Next >
[Bug 1018280] yast bootloader fails on AArch64 if grub2 not installed or grub.cfg unavailable
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 06 Jan 2017 12:00:11 +0000
  • Message-id: <bug-1018280-21960-wye68uyRkR@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1018280
http://bugzilla.opensuse.org/show_bug.cgi?id=1018280#c6

--- Comment #6 from Andreas Färber <afaerber@xxxxxxxx> ---
(In reply to Josef Reidinger from comment #5)
(In reply to Andreas Färber from comment #2)
Created attachment 708872 [details]
y2logs for /etc/default/grub error

This is after:

zypper rm grub2
rm -rf /boot/grub2/
yast bootloader

in this case problem is that rm of grub2 removes also /etc/default/grub so
result is that it failed during initialize of module.

Please keep in mind that the above commands were just to reproduce the virgin
system state. I did not originally run those commands.

Is suitable for you if
we report error and then allow user to prepose configuration from scratch,
which will also install package back? I worry we do not have way how to
restore configuration in such case.

Actually I would've expected that absence of GRUB packges would lead to YaST
selecting "Not Managed" as Boot Loader option. Then, if the user actively
selects "GRUB2 for EFI" and saves with "OK", the same way it installs
kexec-tools it could just install the necessary grub2-* packages.

Observed is that absence of /etc/sysconfig/bootloader leads to a default of
"GRUB2 for EFI", which may in turn cause this module initialization problem.

But yes, if the file is not there I expect YaST to (silently) handle this by
choosing appropriate defaults that the user can then tweak before saving to
disk. Again, if the file never existed, there is no way to restore anything
anyway.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References