| Summary: | preupgrade doesn't properly setup grub for install on reboot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | G.Wolfe Woodbury <redwolfe> |
| Component: | preupgrade | Assignee: | Richard Hughes <richard> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | richard, sheldonh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-16 15:18:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
G.Wolfe Woodbury
2011-05-10 22:47:25 UTC
There is a workaround, edit the grub.conf and correct the "default=" option to boot the new stanza 0. Then reboot again and preupgrade proceeds okay. [I'd have a patch, but I don't do python well, and don't quite understand grubby] Same story here inside VirtualBox 4.0.8r71778, except that after I manually corrected grub.conf, the preupgrade process hangs at "trying to unpack rootfs image as initramfs". (In reply to comment #2) > Same story here inside VirtualBox 4.0.8r71778, except that after I manually > corrected grub.conf, the preupgrade process hangs at "trying to unpack rootfs > image as initramfs". 512MB RAM isn't enough for a Fedora 15 install on a VirtualBox, because a) GNOME3 wants a 3D graphics card, b) VirtualBox takes 3D graphics card memory out of the total allocated for the virtual machine, and c) You really can't complete a Fedora 15 preupgrade in less than 512MB RAM. I completed the install like this: * run preupgrade-cli (or preupgrade) * manually set default=0 in grub.conf, * shut down, * allocate 1024MB RAM, * boot up, * allowing the upgrade to complete and reboot, * waiting for the boot process to appear to hang waiting for plymouth-quit, * logging in as root on another vty (e.g. Alt-F2), * reinstalling the vbox additions: * mount /dev/cdrom /mnt * /mnt/VBoxLinuxAdditions.run * reboot Thereafter, I was able to reduce the total RAM allocation for the VM to 768MB, although that got sluggish, and I've now reverted to 1024MB permanently. Also, the guy who sits next to me ran into the originally reported bug (incorrect default item in grub.conf) during an upgrade on a physical machine. So I think virtuality is a red herring. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |