Bug 1003381

Summary: grub2 selected by trying to configure "bootloader" despite "no bootloader can be installed"
Product: [openSUSE] openSUSE Distribution Reporter: Per Jessen <per>
Component: YaST2Assignee: Josef Reidinger <jreidinger>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium CC: ancor, gsouza, jreidinger, per
Version: Leap 42.2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs as saved by save_y2logs

Description Per Jessen 2016-10-06 15:03:09 UTC
Created attachment 696205 [details]
y2logs as saved by save_y2logs

2016-10-06 16:49:31 <1> install(4193) [Ruby] lib/cheetah.rb:158 Executing "/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg".
2016-10-06 16:49:31 <3> install(4193) [Ruby] lib/cheetah.rb:206 Error output: /usr/sbin/grub2-probe: error: failed to get canonical path of `rootserver:/srv/nfsroot/office36'.
2016-10-06 16:49:31 <3> install(4193) [Ruby] lib/cheetah.rb:178 Status: 1
2016-10-06 16:49:31 <3> install(4193) [Ruby] yast2/execute.rb:66 Execution of command "[["/usr/sbin/grub2-mkconfig", "-o", "/boot/grub2/grub.cfg"]]" failed.
Exit code: 1
Error output: /usr/sbin/grub2-probe: error: failed to get canonical path of `rootserver:/srv/nfsroot/office36'.
Comment 1 Per Jessen 2016-10-06 15:30:56 UTC
Weird - it looks like grub2 got installed despite my deselecting it.
Comment 2 Per Jessen 2016-10-07 06:45:22 UTC
Although I deselected grub2, it was automatically re-selected when I clicked on "Bootloader".  This said "booting from NFS, no bootloader can be installed", after which I see grub2 having been re-selected.  Having grub2 installed causes weird and wonderful problems.
Comment 3 Ancor Gonzalez Sosa 2016-10-07 09:13:29 UTC
Per. Even if it's not possible, the installer is trying to install grub2 because that is what is selected in the "booting" section of the final installation settings.

If you click on "booting" and select "Not Managed" in the "Boot Loader" field of the "Boot Loader Settings" screen, grub2 should not be installed. Can you please try that?
Comment 4 Josef Reidinger 2016-10-07 09:22:50 UTC
it should be handled automatic. Problem here is that it sets grub2 bootloader, but in fact for nfs root, it is special handling, but not in packages list. Will fix it for TW
Comment 5 Josef Reidinger 2016-10-07 09:23:38 UTC
question is what is correct way. Propose to use no bootloader or use grub2 and skip doing action there.
Comment 6 Per Jessen 2016-10-07 13:43:46 UTC
(In reply to Ancor Gonzalez Sosa from comment #3)
> Per. Even if it's not possible, the installer is trying to install grub2
> because that is what is selected in the "booting" section of the final
> installation settings.
> 
> If you click on "booting" and select "Not Managed" in the "Boot Loader"
> field of the "Boot Loader Settings" screen, grub2 should not be installed.
> Can you please try that?

Hi Ancor

in this scenario, when I click on booting, I'm just given a message "No bootloader config possible" (or something like that). 

(in reply to Josef Reidinger)
> question is what is correct way. Propose to use no bootloader or use grub2 and > skip doing action there.

The current reaction (bootloader cannot be used) is good, except it still installs grub2 :-)
Comment 7 Per Jessen 2016-10-09 08:56:47 UTC
*** Bug 1003802 has been marked as a duplicate of this bug. ***
Comment 8 Per Jessen 2016-10-10 08:23:12 UTC
*** Bug 1003686 has been marked as a duplicate of this bug. ***
Comment 9 Josef Reidinger 2017-09-15 13:33:00 UTC
gilson - is this fixed also with fix for bug#1014167
Comment 10 Josef Reidinger 2018-02-06 16:16:03 UTC
I see one of the latest test run and it really does not force grub2