[Bug 883528] New: bootloader module of YaST2 does not change default system to boot
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c0 Summary: bootloader module of YaST2 does not change default system to boot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: freek@opensuse.org QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 I installed on separate partitions, root and home, openSUSE Factory. I also updated this system on Jun 20, 2014 to the newest factory repository. I have several systems, 13.1, 12.3 and 12.2 on my two disks; root discs all on /dev/sda. The grub2 boot menu generated with Factory shows all these systems. The default system to boot is Factory, shown as openSUSE. However I want 13.1 to be the default, so I tried to change that using the module bootloader from YaST2. Despite the fact that this module shows 13.1 to be the default, when booting still Factory will be booted. So I tried to change that also in 13.1, but here I have the same problem. The interface looks different, and shows that 13.1 is the default to be booted, however when booting still Factory is the default. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfilka@suse.com AssignedTo|yast2-maintainers@suse.de |jreidinger@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c1 --- Comment #1 from Freek de Kruijf <freek@opensuse.org> 2014-06-24 10:41:13 UTC --- I updated the factory system and noticed that updating package mdadm took quite some time, so I assumed post processing did something with the bootloader grub2, because afterward the default system to boot was openSUSE 13.1 like it is in the configuration. So I ran the YaST module bootloader in the Factory system and now despite an unchanged configuration the default system to boot when starting the system was again Factory. After that I did a "zypper in --force mdadm" in the Factory system after which starting the system now boots the 13.1 system as the default. So apparently post processing of mdadm does something different, but the right thing, than the YaST module bootloader. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c2 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mchang@suse.com --- Comment #2 from Josef Reidinger <jreidinger@suse.com> 2014-06-26 12:25:24 UTC --- Micheal - I check code and we do not set default in perl-Bootloader. It always write saved. I see that you write that code, is it intention or just forgotten? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c3 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang@suse.com --- Comment #3 from Michael Chang <mchang@suse.com> 2014-06-27 04:37:47 UTC --- Yes, it is intentional. The 'saved' is a special string that make grub to read the default boot entry from variables stored in external environment block file (/boot/grub2/grubenv) instead from the grub.cfg. The default entry is written to environment block via grub2-set-default and also grub2-reboot for saved_default. The grub.cfg would refer to environment block and variables and react accordingly. This is required for features like grub-once to work because environment block maybe updated in grub, athough not all file systems and disk abstractions supports it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c4 --- Comment #4 from Michael Chang <mchang@suse.com> 2014-06-27 05:02:17 UTC --- Hi Freek, I think we need to define "default system". It's not clear to me the meaning of default here because it can be: 1. The default system booted, then use it as a jump start to other systems. The default system booted may change to others that have bootloader reinstallation happened and hijack the boot path by writing it's MBR. 2. The default boot entry in the boot menu. This is manged by YaST module. Please make sure your default booted system is factory and then then try change the default boot entries via yast ..? 1. Booting to factory 2. reinstall bootloader (by update-bootloader --reinit) 3. Run yast bootloader modules to set default entry to boot 4. reboot and see if boot menu is factory and default boot entry has changed (to 13.1). Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c5 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|mchang@suse.com |freek@opensuse.org --- Comment #5 from Josef Reidinger <jreidinger@suse.com> 2014-06-27 07:15:35 UTC --- set correctly need info -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c6 Freek de Kruijf <freek@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|freek@opensuse.org | --- Comment #6 from Freek de Kruijf <freek@opensuse.org> 2014-06-27 11:24:48 UTC --- I meant item 2. When starting the system and the grub2 timeout elapses the default system is the system that will be booted. I installed Factory which generates a new grub2 where Factory will be the default system to boot after timeout. After several times booting Factory I wanted the default system to boot to be 13.1, so I used YaST in Factory to change the default from Factory to 13.1. I also have a 12.3 and 12.2 system, which are also present in the grup2 bootmenu. However YaST shows that the 13.1 is the default system, but when booting the computer I have to select 13.1 to boot that system. After the timeout Factory will be booted. I also tried to generate a new grub2 in 13.1 using YaST, it shows 13.1 is the default to be booted system, however nothing changes and after the timeout Factory will be booted. So also the bootloader of YaST in 13.1 is at fault. I tried changing the default to Factory, generated a new grub2, started the bootloader module again, changed the default system back to 13.1 and generated a new grub2, all in 13.1. But no avail. After a timeout Factory will be booted. Only after a forced (re)installation of mdadm in Factory, I got a grub2 that boots 13.1 after the timeout. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c7 --- Comment #7 from Freek de Kruijf <freek@opensuse.org> 2014-06-27 12:25:07 UTC --- Booted Factory. Gave the command update-bootloader --reinit Booted. Grub2 shows the default is 13.1 Booted however Factory. Used YaST bootloader to change default to Factory. Booted. Grub2 shows Factory as default. Booted Factory. Used YaST bootloader to change default to 13.1 Booted. Grub2 shows 13.1 as default. OK now!!! Back in 13.1 to write this comment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c8 --- Comment #8 from Freek de Kruijf <freek@opensuse.org> 2014-06-28 11:54:50 UTC --- I reported this as a 13.1 bug and it still is a 13.1 bug in my view. Starting YaST bootloader in 13.1 I changed the default system to boot to Factory, it was 13.1; Factory shows as openSUSE 20140623. However finishing the bootloader and starting the system again, grub2 still shows 13.1 as the default system. It looks as if nothing has changed in grub2. Even after update-bootloader --reinit in 13.1 nothing changes. I am sure in previous versions I had the possibility to generate a new booting system by scanning all disks/partitions. However in 13.1 and apparently also in Factory this ability has vanished. I keep the default not to write to MBR. Should I change that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c9 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |freek@opensuse.org --- Comment #9 from Josef Reidinger <jreidinger@suse.com> 2014-07-01 11:55:02 UTC --- It should not depend if stage 1 is written to MBR or not. Can you please attach your logs, so I can check if grub2-set-default always succeed? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c10 --- Comment #10 from Josef Reidinger <jreidinger@suse.com> 2014-07-01 11:57:12 UTC --- Also if you can after each attemp try to capture output of /usr/bin/grub2-editenv list this should show what default is set. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c11 Freek de Kruijf <freek@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|freek@opensuse.org | --- Comment #11 from Freek de Kruijf <freek@opensuse.org> 2014-07-01 15:32:23 UTC --- Created an attachment (id=596860) --> (http://bugzilla.novell.com/attachment.cgi?id=596860) y2log.xz compressed y2log from 10:01 this morning -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c12 --- Comment #12 from Freek de Kruijf <freek@opensuse.org> 2014-07-01 15:34:15 UTC --- This morning I updated Factory and ended up with grub2 having the default system to boot to be Factory again, although YaST bootloader indicates 13.1 should be the default. I tried reinstallation of mdadm, to get the default to be 13.1 again, but this failed. This morning at 10:01 I did run the YaST boorloader again. It indicated 13.1 to be the default, however Factory is still the default. I will attach the part of y2log compressed with xz from this time on to this bug. On the 13.1 system I have: @eik131:~> grub2-editenv list saved_entry=openSUSE 20140623 (x86_64) (op /dev/sda9) Will add the same output from Factory later. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c13 --- Comment #13 from Freek de Kruijf <freek@opensuse.org> 2014-07-01 15:45:50 UTC --- On Factory: @eik132:~> /usr/bin/grub2-editenv list saved_entry=openSUSE 13.1 (x86_64) (op /dev/sda3) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=883528 https://bugzilla.novell.com/show_bug.cgi?id=883528#c14 --- Comment #14 from Freek de Kruijf <freek@opensuse.org> 2014-08-07 19:06:51 UTC --- After updating Factory, often a new boot system is generated. In that case the default system to boot is always changed into booting Factory. Starting the bootloader module of yast2 shows that the configuration is still indicating openSUSE 13.1 as the default system to boot. So apparently during the update this configuration is not used to generate the grub2 boot system. I have to change the default system to boot to something other than the current default, after finishing the generation a new generation is started to finally get openSUSE 13.1 to be the default system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com