[Bug 239674] Re: ucf and update-grub semantics are incompatible
There is another way to install Ubuntu without using D-I or FAI, and that is VMBuilder. -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239674] Re: ucf and update-grub semantics are incompatible
@Sergey: but not in a real world datacenter ;) -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239674] Re: ucf and update-grub semantics are incompatible
Well, guys, if you install an Ubuntu Server or Desktop with FAI it's totally different from a kickstart+D-I preseeding auto install. The ucf + grub/menu.lst handling is working when using the kickstart + D-I preseeding installation method, but it's not usable (without the workaround) when using FAI. Grub2 istallation is working fine in the latest FAI version and Ubuntu auto Install the FAI way...That's the reason why I do think the bugreport, (which was filed as report to the ubuntu fai team) is a won't fix. Regarding the fact, that someone could change the menu.lst manually, that someone has to know how to disable ucf and how to deal with kernel upgrades manually. But that's my reasoning for setting this bug to won't fix Regards, \sh -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239674] Re: ucf and update-grub semantics are incompatible
the bugreport, (which was filed as report to the ubuntu fai team) No, it wasn't. -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239674] Re: ucf and update-grub semantics are incompatible
@steve: sorry...I found this bug via ubuntu fai teamjust checked the activity...you are right. \sh -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239674] Re: ucf and update-grub semantics are incompatible
I don't agree with that rationale of marking it won't fix. Regardless of whether FAI has a documented workaround for this bug, this is a bug in Ubuntu's grub package, where a normal user interaction with the grub configuration file leads to extremely strange results and an unbootable system. There are other ways to encounter this situation besides FAI, such as any configuration management system that wants to update the general initial settings in the menu.lst file. ** Changed in: grub (Ubuntu) Status: Won't Fix = New -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239674] Re: ucf and update-grub semantics are incompatible
I agree that's not a good rationale for a wontfix here. FWIW, the long-term solution expected here is that we will convert systems from grub1 to grub2 on upgrade to lucid, at which point all the ucf handling goes away because we have a sensible config file format; which means that unfortunately the bug in grub1 (which I agree is a bug, and I regret not noticing when this was being developed) isn't likely to receive further attention before the grub package becomes obsolete entirely. -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239674] Re: ucf and update-grub semantics are incompatible
Marking it as Won't fix. As Patrick wrote the fix is http://faiwiki.informatik.uni-koeln.de/index.php/FAIUbuntuGrubProblems :) Regards, \sh ** Changed in: grub (Ubuntu) Status: New = Won't Fix -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239674] Re: ucf and update-grub semantics are incompatible
I just want to add a me too for this bug. I'm not using any custom kernels, but I just have a noninteractive script that does my software updates, so I set UCF_FORCE_CONFFOLD=YES in the script and this causes nothing but problems for grub menu.lst configuration. Thanks to this bug report, it does seem that I can do this to workaround the problem in my script: unset UCF_FORCE_CONFFOLD export UCF_FORCE_CONFFNEW=YES ucf --purge /var/run/grub/menu.lst update-grub I have spent hours trying to figure out why update-grub would say it found new kernels, yet, never update the menu.lst. There should at least be an error message of some sort if the menu.lst didn't actually get updated with the kernels it said it found. For example, without purging /var/run/grub/menu.lst here is the output of update-grub with no UCF environment variables set: Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.24-21-generic Found kernel: /boot/vmlinuz-2.6.24-19-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done At this point menu.lst does not have the 2.6.24-21-generic kernel. This kernel was installed with my noninteractive script, so UCF_FORCE_CONFFOLD=YES would have been set when it was initially installed. -- ucf and update-grub semantics are incompatible https://bugs.launchpad.net/bugs/239674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
