updated kernel not used by default

[Chris Murphy]

On Sep 14, 2014, at 8:38 AM, Joshua Andrews <woodguy552010 at gmail.com> wrote:

> 
> 
> On Sat, Sep 13, 2014 at 12:13 PM, Chris Murphy <lists at colorremedies.com> wrote:
> Got a bug where the upgraded kernel isn't being booted by default. I'm not exactly sure why, or what release criteria to use, so I set it to final based on it being a security concern.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1141414
> 
> 
> It seems that save_env is not happening in the function savedefault.
> 
> My grubenv says:
> # GRUB Environment Block
> saved_entry=Fedora (3.16.2-300.fc21.x86_64) 21 (Twenty One)
> 
> But I'm running; 3.16.2-301.fc21.x86_64, and I've booted this kernel 3 times but grub always selects 3.16.2-300.fc21.x86_64. 
> 
> Anyway, it might be related.

The anaconda program.log shows that it called 'grub2-set-default 0'. But if post-install, while still booted in the install environment, I do:
# chroot /mnt/sysimage
# grub2-editenv list
saved_entry=Fedora, with Linux 3.16.1-301.fc21.i686

If I then do
# grub2-set-default 0
# grub2-editenv list
saved_entry=0


So the problem is that the saved_entry is wrong from the outset. I just don't know why 'grub2-set-default 0' from within anaconda isn't sticking. Or if something else is changing the grubenv? Hmmm… Still in the chroot in the live environment:

# grep grub2 /var/log/anaconda/program.log 
14:31:41,028 INFO program: Running... grub2-install --no-floppy /dev/sda
14:31:42,323 INFO program: Running... grub2-set-default 0
14:31:42,366 INFO program: Running... grub2-mkconfig -o /boot/grub2/grub.cfg


What are the odds that grub2-install hasn't completed yet, by the time grub2-set-default is issue?

# rm -rf /boot/grub2/*
# grub2-set-default 0
# grub2-editenv list
saved_entry=0
# grub2-install --no-floppy /dev/sda
# grub2-editenv list
saved_entry=0
# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.16.1-301.fc21.i686
Found initrd image: /boot/initramfs-3.16.1-301.fc21.i686.img
Found linux image: /boot/vmlinuz-0-rescue-960cd0d2079741f49d30265c1b1863a8
Found initrd image: /boot/initramfs-0-rescue-960cd0d2079741f49d30265c1b1863a8.img
done
# grub2-editenv list
saved_entry=0

*sigh* WTF?

OK here's another idea, maybe the /etc/grub/default isn't written yet at the time all of this happens? Because there's a line in there: GRUB_DEFAULT=saved which seems wrong. I think that should be GRUB_DEFAULT=0. But let's find out. Still in chroot:

# rm -f /etc/default/grub
# rm -rf /boot/grub2/*
## And now proceed to try various permutations of the program.log commands…

But in every case, grub2-editenv list shows saved_entry is 0. Manually, I never get saved_entry=Fedora, with Linux 3.16.1-301.fc21.i686.

Grrr….


Chris Murphy