http://bugzilla.opensuse.org/show_bug.cgi?id=929594
http://bugzilla.opensuse.org/show_bug.cgi?id=929594#c12
Josef Reidinger
Further info.
I just upgraded another system from 13.1 to 13.2, using "zypper dup". It now has no bootloader configured under YaST2.
yes, yast2-bootloader no longer support grub1, but you can still manage to use it, just without yast. So if you use zypper dup, then it usually just works and only if you need modification you need to upgrade to grub2 and manage it yourself. More user friendly message in y2-bl that grub1 is no longer support is tracked as different bug number.
It was using Grub v1. Now I see that Grub v1 is not listed as an option, so I'm guessing Grub was uninstalled as part of the update. I was never given any warning that I no longer had a bootloader configured.
It is configured, just y2-bl cannot handle it.
Why was I using Grub 1? I couldn't get Grub 2 to boot. I tried again and again and gave up. So it would have been nice if Grub 1 hadn't gone away like that.
If you report your scenario and problem we can look at it. Only think I am aware of is bigger space needed for stage 2 that cause in not so common cases problem.
Maybe I can make Grub 2 work, but assume for a moment that I haven't noticed that I have no bootloader configured. Now I have the same issue that was described at the start of this report. The system silently continues to run with the old kernel from before the upgrade, and it never updates.
Only if you run yast2-bootloader, otherwise it is automatic updated to new kernel by perl-bootloader. As I said this problem in yast2 bootloader is covered by bug#923458
Please don't mark this invalid again. There is a problem affecting everyone who follows your "supported" upgrade path with a bootloader that is going to be silently removed during the update.
It should not be silently removed. If you do not run yast2-bootloader it should just work without any issue. If it is not case, I will need logs to see what happens. So marking as dup for UX problem that y2-bl do not nicely report that old grub1 configuration is used. *** This bug has been marked as a duplicate of bug 923458 *** -- You are receiving this mail because: You are on the CC list for the bug.