Red Hat Bugzilla – Bug 835704
your current installation cannot be upgraded
Last modified: 2013-01-10 01:50:39 EST
Description of problem: Plain F16 x86_64 system, yum upgraded from some Fxx install through F16, never skipping any release. Boots fine, knows it is F16. Small (200 MB) /dev/sda1 on /boot. LVM on /dev/sda2 with 5 GB swap and 150 GB root. Trying to upgrade via DVD complains "your current installation cannot be upgraded". Version-Release number of selected component (if applicable): anaconda from F17 DVD How reproducible: Always Steps to Reproduce: 1. Load F17 DVD, run through install Actual results: Complains version is too old, refuses to update Expected results: Update proceeding normally. Additional info: I cloned the system into a different disk (with a larger /boot so preupgrade may work as system is on fixed IP, thus getting stage2 doesn't work as the DHCP assigned IP can't get through the firewall...) and put the disk on a spare computer, thus can test this if someone wants to find out the cause. We'll need to upgrade the system though. Fresh install is not a nice option
What does /etc/redhat-release have in it? Also, please attach the logs from /tmp/*log as individual text/plain files.
/etc/redhat-releasee (as well as fedora-release) contains Fedora release 16 (Verne) Will attaching all logs
Created attachment 594627 [details] anaconda.log
Created attachment 594628 [details] storage.log
Created attachment 594629 [details] program.log
Created attachment 594630 [details] X.log
Created attachment 594631 [details] syslog
It doesn't seem to like your release string, even though what you posted in comment 2 looks fine: 16:09:43,457 INFO storage: product None, version None, arch x86_64 found on penguin_vg-root is not upgradable 16:09:43,457 DEBUG storage: test results: {'product': False, 'version': False, 'arch': True}
I think I found the problem/bug. I have a real file: /etc/fedora-release containing: Fedora release 16 (Verne) I have a symlink pointing to it via a relative path: /etc/system-release -> fedora-release I have another symlink pointing to that symlink, using an absolute path: /etc/redhat-release -> /etc/system-release When anaconda runs from the DVD the absolute path doesn't really point to my fedora-release file. I changed system-release to point directly/relatively to fedora-release and now anaconda finds my system and wants to updated. I'm pretty sure I didn't create or mess with any of the files above, and they are just as created by my initial install and yum upgraded systems ...
Just looked at my two remaining F16 systems, besides the one where I saw this problem, and in them both /etc/system-release and /etc/redhat-release are symlinks pointing to fedora-release (relative), so the problem existed on only one of my machines.
Really points to some local misconfiguration or one-shot bug. Not much we can do about that here/now.
*** Bug 887494 has been marked as a duplicate of this bug. ***
Seems like Sandro (comment 12 here, and bug 887494) ran into the same problem, so now we have two people which had the same local misconfiguration, or, most likely, the result of a previous upgrade, as I'm pretty sure I never touched those files. Probably a moot problem by now, unless someone runs into going from f71 to f18.