Red Hat Bugzilla – Bug 536739
anaconda of preupgrade can not start after reboot on ppc
Last modified: 2014-01-21 18:12:25 EST
Description of problem:
install f11 and preupgrade, following these steps to upgrade:
run preupgrade command in terminal,when the process completes(after all packages download finished,prompt user to reboot), click Reboot,system automatically booted into f11, the anaconda did not start to finish upgrade.
Version-Release number of selected component (if applicable):
reboot system, the anaconda should start to upgrade automatically
Liam, can you supply the output from `preupgrade 2>&1|tee /tmp/preupgrade.log` and the /etc/yaboot.conf file prior to rebooting the system?
Additionally, did you update your F-11 system using 'yum update' prior to running preupgrade? Can you provide `rpm -q yaboot` as well?
I might not have time to reproduce this today, but will reply with feedback if I'm able to. I think those 2 files should help us determine where the problem exists.
Created attachment 369170 [details]
it seems that the default boot is not upgrade, still be the original kernel.This is the reason that system can not finish upgrade automatically?
This the log of preupgrade:
/usr/lib/python2.6/site-packages/yum/__init__.py:203: UserWarning: Use .preconf instead of passing args to _getConfig
warnings.warn('Use .preconf instead of passing args to _getConfig')
Loaded plugins: blacklist, fastestmirror, refresh-packagekit, whiteout
Detected in-progress upgrade to Rawhide
Loading mirror speeds from cached hostfile
* fedora: fedora.mirrors.hkt.cc
* updates: ftp.kddilabs.jp
Not using downloaded repomd.xml because it is older than what we have:
Current : Wed Nov 11 07:08:10 2009
Downloaded: Tue Nov 10 06:46:52 2009
Fetched treeinfo from http://ftp.riken.jp/Linux/fedora/development/ppc/os//.treeinfo
treeinfo timestamp: Tue Nov 10 07:07:46 2009
/boot/upgrade/vmlinuz checksum OK
/boot/upgrade/ramdisk.image.gz checksum OK
Not enough space in /boot/upgrade to download install.img.
Checking for new repos for mirrors
* preupgrade: ftp.kddilabs.jp
it gave information: "Not enough space in /boot/upgrade", How big of the install.img
I have about 123M in /boot partition:
Filesystem Size Used Avail Use% Mounted on
58G 4.0G 51G 8% /
/dev/sda2 194M 62M 123M 34% /boot
tmpfs 3.8G 848K 3.8G 1% /dev/shm
#du -h /boot/*
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.