http://bugzilla.opensuse.org/show_bug.cgi?id=1018280 http://bugzilla.opensuse.org/show_bug.cgi?id=1018280#c2 --- Comment #2 from Andreas Färber --- Created attachment 708872 --> http://bugzilla.opensuse.org/attachment.cgi?id=708872&action=edit y2logs for /etc/default/grub error This is after: zypper rm grub2 rm -rf /boot/grub2/ yast bootloader -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1018280 http://bugzilla.opensuse.org/show_bug.cgi?id=1018280#c4 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|yast2-maintainers@suse.de |jreidinger@suse.com --- Comment #4 from Josef Reidinger --- thanks, I will check it -- You are receiving this mail because: You are on the CC list for the bug.

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 --- (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.

http://bugzilla.opensuse.org/show_bug.cgi?id=1018280 http://bugzilla.opensuse.org/show_bug.cgi?id=1018280#c8 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com Flags| |needinfo?(jsrain@suse.com) --- Comment #8 from Josef Reidinger --- ah, so original problem is absence of /etc/sysconfig/bootloader, in which case we propose default. I see a bit risky to use not-managed as from our POV it is broken configuration. My suggestion is to report it to user and allow him to repropose it from scratch and tweak it as needed and then ensure it will work after setting such configurarion. jsrain - what do you think? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1018280 http://bugzilla.opensuse.org/show_bug.cgi?id=1018280#c10 --- Comment #10 from Andreas Färber --- (In reply to Alexander Graf from comment #9)

We could also add a dummy /etc/sysconfig/bootloader inside the JeOS-rootfs target that sets it to "no bootloader". That way the image we generate would end up consistently.

Sounds like a plan: zypper rm grub2 rm -rf /boot/grub2/ # edit /etc/sysconfig/bootloader to have LOADER_TYPE="none" yast bootloader However, in that case manually selecting "GRUB2 for EFI" and then switching to the "Bootloader Options" tab leads to an error for /usr/bin/grub2-editenv. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1018280 http://bugzilla.opensuse.org/show_bug.cgi?id=1018280#c12 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jsrain@suse.com) | --- Comment #12 from Josef Reidinger --- (In reply to Alexander Graf from comment #9)

We could also add a dummy /etc/sysconfig/bootloader inside the JeOS-rootfs target that sets it to "no bootloader". That way the image we generate would end up consistently.

I would prefer not to change the default configuration for a non-existent entry to "no bootloader" since IIUC that default may get used during installation - and there we basically always want to have grub2-efi.

sounds good for me (In reply to Andreas Färber from comment #10)

(In reply to Alexander Graf from comment #9)

...

We could also add a dummy /etc/sysconfig/bootloader inside the JeOS-rootfs target that sets it to "no bootloader". That way the image we generate would end up consistently.

Sounds like a plan:

zypper rm grub2 rm -rf /boot/grub2/ # edit /etc/sysconfig/bootloader to have LOADER_TYPE="none" yast bootloader

However, in that case manually selecting "GRUB2 for EFI" and then switching to the "Bootloader Options" tab leads to an error for /usr/bin/grub2-editenv.

yeah, that is real bug, I will fix it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1018280 http://bugzilla.opensuse.org/show_bug.cgi?id=1018280#c14 --- Comment #14 from Andreas Färber --- (In reply to Andreas Färber from comment #10)

However, in that case manually selecting "GRUB2 for EFI" and then switching to the "Bootloader Options" tab leads to an error for /usr/bin/grub2-editenv.

... but if I just select OK after the selection, it installs grub2-arm64-efi as expected and after a while finishes fine. -- You are receiving this mail because: You are on the CC list for the bug.