Re: A preupgrade adventure - F16 to F17
On Sat, 2012-07-21 at 12:21 +0200, Reindl Harald wrote: Am 21.07.2012 01:41, schrieb Martin Langhoff: Hmm, now I think it was a F14 install: ls -lah /root/anaconda-ks.cfg -rw---. 1 root root 837 Jun 13 2011 /root/anaconda-ks.cfg Who calls grubby and ignores its ungraceful death? That needs bubble up the call stack... Upgrade completed without any more hiccups. Moving to grub2 the move to grub2 should have been dobe in the F16 cycle http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_15_-.3E_Fedora_16 look at Bootloader change this may be a big change on older setups because you have to make sure there is enough space for GRUB2 meaning on all my machines installed in 2008 make free space before the /boot partition that is why the movement to grub2 is not done automatically It is, if you upgrade via anaconda, but not if you upgrade via yum. We couldn't find an acceptable method to trigger a bootloader upgrade via yum. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: A preupgrade adventure - F16 to F17
Am 21.07.2012 01:41, schrieb Martin Langhoff: Hmm, now I think it was a F14 install: ls -lah /root/anaconda-ks.cfg -rw---. 1 root root 837 Jun 13 2011 /root/anaconda-ks.cfg Who calls grubby and ignores its ungraceful death? That needs bubble up the call stack... Upgrade completed without any more hiccups. Moving to grub2 the move to grub2 should have been dobe in the F16 cycle http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_15_-.3E_Fedora_16 look at Bootloader change this may be a big change on older setups because you have to make sure there is enough space for GRUB2 meaning on all my machines installed in 2008 make free space before the /boot partition that is why the movement to grub2 is not done automatically signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
A preupgrade adventure - F16 to F17
Just an informational anecdote. My main dev machine is a vanilla Lenovo X220 laptop, running an up-to-date F16. At OLPC, we are damned close to *shipping* a F17-based distro on our XO laptops, so I thought it'd be good to update. Worried about /usr move, I decided to DTRT: use preupgrade. First, preupgrade completely hides grubby errors, and tells you everthing's peachy. This cannot be a feature. I managed to hit a few grubby errors, and without the debug output from preupgrade-cli showing the grubby command it's running, I'd still be scratching my head... So grub configs were not being updated, for two reasons - My machine does not have /boot/grub/grub.cfg, it has grub.conf instead, so I hit BZ#841976 . Unsure why these conffiles are changing names, this was a fresh F16 install back when F16 was new. - Added the missing grub.cfg, grubby segfaults (BZ#841979). Ummpf! - The preupgrade wikipage helpfully provides instructions to edit grub.conf by hand. Completely wrong instructions. You don't want the /boot prefix there. You don't want savedefault. You probably want to ensure you see the menu. I am no expert on what params the preupgrade initrd _really_ needs, but things did not move forward until I fixed it up and added the params that preupgrade was giving to the failing grubby. - And there I hit BZ#813973 - preupgrade (anaconda) garbles the URL so you only get 404s. The adventure continues, but at thistime I am under the impression that preupgrade gets far less testing and polish than yum upgrades. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: A preupgrade adventure - F16 to F17
On Fri, 2012-07-20 at 14:28 -0400, Martin Langhoff wrote: Just an informational anecdote. My main dev machine is a vanilla Lenovo X220 laptop, running an up-to-date F16. At OLPC, we are damned close to *shipping* a F17-based distro on our XO laptops, so I thought it'd be good to update. Worried about /usr move, I decided to DTRT: use preupgrade. First, preupgrade completely hides grubby errors, and tells you everthing's peachy. This cannot be a feature. I managed to hit a few grubby errors, and without the debug output from preupgrade-cli showing the grubby command it's running, I'd still be scratching my head... So grub configs were not being updated, for two reasons - My machine does not have /boot/grub/grub.cfg, it has grub.conf instead, so I hit BZ#841976 . Unsure why these conffiles are changing names, this was a fresh F16 install back when F16 was new. - Added the missing grub.cfg, grubby segfaults (BZ#841979). Ummpf! - The preupgrade wikipage helpfully provides instructions to edit grub.conf by hand. Completely wrong instructions. You don't want the /boot prefix there. You don't want savedefault. You probably want to ensure you see the menu. I am no expert on what params the preupgrade initrd _really_ needs, but things did not move forward until I fixed it up and added the params that preupgrade was giving to the failing grubby. - And there I hit BZ#813973 - preupgrade (anaconda) garbles the URL so you only get 404s. The adventure continues, but at thistime I am under the impression that preupgrade gets far less testing and polish than yum upgrades. Um. I think you might be working from a completely false premise. If you did a fresh install of Fedora 16 you should have grub2. Not grub. The way grubby works, if you have a grub2-based system it'll 'complain' about the lack of a grub1 config file sometimes, but this isn't a problem in itself and can be ignored; if something's going wrong, that isn't the reason why. The file that needs to be updated is /boot/grub2/grub.cfg (/etc/grub2.cfg is a symlink to it). Note that once you reach the point of bootloader configuration, preupgrade did its job long ago. You're now just using plain anaconda. However, due to a bit of an oversight, a preupgrade-based upgrade uses a different anaconda bootloader config management option to what a DVD/netinst-based upgrade would use. In practice, though, it mostly works. (preupgrade upgrades do 'update existing bootloader configuration'; DVD/netinst upgrades do 'write new bootloader configuration'). I'm really a bit confused by exactly what bootloader you actually have installed, having read your bug reports, but it doesn't look much like a 'fresh F16 install' to me... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: A preupgrade adventure - F16 to F17
On Fri, Jul 20, 2012 at 6:55 PM, Adam Williamson awill...@redhat.com wrote: Um. I think you might be working from a completely false premise. If you did a fresh install of Fedora 16 you should have grub2. Not grub. Hmmm. This laptop has had F14, but IIRC it got a wipe-and-reinstall treatment. You may be right on that point... The way grubby works, if you have a grub2-based system it'll 'complain' about the lack of a grub1 config file sometimes, but this isn't a problem in itself and can be ignored; if something's going wrong, that isn't the reason why. The file that needs to be updated is /boot/grub2/grub.cfg (/etc/grub2.cfg is a symlink to it). /boot/grub2 exists, but is empty. So preupgrade / grubby don't work with grub, and should bail out if grub is the bootloader? Should that be my bug report? Note that once you reach the point of bootloader configuration, preupgrade did its job long ago. You're now just using plain anaconda. Preupgrade is driving, at least in the prep stage, so I'll file those bugs against preupgrade. Up to preupgrade maintainers to know more about who to blame ;-) However, due to a bit of an oversight, a preupgrade-based upgrade uses a TBH, I think that BZ#813973 is a high value bug that affects all small boot partition users, it should be fixed, or at least then known workaround noted in the wikipage. I'm really a bit confused by exactly what bootloader you actually have Plain grub. I apologize, this may be a F14-F16 box. Cannot check right now, it is finally upgrading... If old grub is no longer the cool thing, I'll try to replace it with grub2 once my upgrade is complete. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: A preupgrade adventure - F16 to F17
On Fri, 2012-07-20 at 19:26 +, Martin Langhoff wrote: On Fri, Jul 20, 2012 at 6:55 PM, Adam Williamson awill...@redhat.com wrote: Um. I think you might be working from a completely false premise. If you did a fresh install of Fedora 16 you should have grub2. Not grub. Hmmm. This laptop has had F14, but IIRC it got a wipe-and-reinstall treatment. You may be right on that point... The way grubby works, if you have a grub2-based system it'll 'complain' about the lack of a grub1 config file sometimes, but this isn't a problem in itself and can be ignored; if something's going wrong, that isn't the reason why. The file that needs to be updated is /boot/grub2/grub.cfg (/etc/grub2.cfg is a symlink to it). /boot/grub2 exists, but is empty. So preupgrade / grubby don't work with grub, and should bail out if grub is the bootloader? Should that be my bug report? Note that once you reach the point of bootloader configuration, preupgrade did its job long ago. You're now just using plain anaconda. Preupgrade is driving, at least in the prep stage, so I'll file those bugs against preupgrade. Up to preupgrade maintainers to know more about who to blame ;-) All preupgrade really does is download a bunch of packages and an anaconda image, set the packages up as a repository, write a kickstart file and create a bootloader entry to boot the anaconda image with the kickstart file. The kickstart tells anaconda to run an upgrade using the repository of packages. As far as bootloader config goes, here is absolutely all that preupgrade does: bootloader --upgrade --location=none it writes that line into the kickstart file (in your case; it can write different lines depending on circumstances). That's *all* it does. That tells anaconda to update the existing bootloader config. It's all on anaconda and grubby after that. If you're hitting an actual bug here, I would nominate grubby as the most likely culprit. I don't think I'd call the bug 'it doesn't work with grub1 and should bail out if it finds it'. Really, anaconda/grubby still ought to be capable of updating grub1 configs, though I doubt this ever got tested. If it's broken, I'd say the bug is just that it's broken, not that it should be prohibited. (Though devs may say otherwise). However, due to a bit of an oversight, a preupgrade-based upgrade uses a TBH, I think that BZ#813973 is a high value bug that affects all small boot partition users, it should be fixed, or at least then known workaround noted in the wikipage. Yeah, we do need to get it on the wiki. I do wish it would get fixed, but we're waiting on preupgrade maintainers for that :/ I'll try and throw it on commonbugs today. I'm really a bit confused by exactly what bootloader you actually have Plain grub. I apologize, this may be a F14-F16 box. Cannot check right now, it is finally upgrading... If old grub is no longer the cool thing, I'll try to replace it with grub2 once my upgrade is complete. In practice, yeah, just getting it onto grub2 - either before the preupgrade or after - is likely the simplest way out of your problem. To a rough approximation, we pretty much expect F16+ systems to be using grub2. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: A preupgrade adventure - F16 to F17
On Fri, Jul 20, 2012 at 4:09 PM, Adam Williamson awill...@redhat.com wrote: On Fri, 2012-07-20 at 19:26 +, Martin Langhoff wrote: On Fri, Jul 20, 2012 at 6:55 PM, Adam Williamson awill...@redhat.com wrote: Um. I think you might be working from a completely false premise. If you did a fresh install of Fedora 16 you should have grub2. Not grub. Hmmm. This laptop has had F14, but IIRC it got a wipe-and-reinstall treatment. You may be right on that point... Hmm, now I think it was a F14 install: ls -lah /root/anaconda-ks.cfg -rw---. 1 root root 837 Jun 13 2011 /root/anaconda-ks.cfg Given the date, it could be F15, but I skipped it because OLPC ships F14 and it was early stages of systemd transition. I prefer to pick my battles :-) (Kidding -- systemd is great on our XOs. ) All preupgrade really does is download a bunch of packages and an anaconda image, set the packages up as a repository, write a kickstart Thanks for the education! Happy to see it re-assigned to anaconda, or grubby. Assigning it to preupgrade (in my pre-enlightened condition) worked a charm. Who calls grubby and ignores its ungraceful death? That needs bubble up the call stack... In practice, yeah, just getting it onto grub2 - either before the preupgrade or after - is likely the simplest way out of your problem. Upgrade completed without any more hiccups. Moving to grub2. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
