Description of problem: Fedora 11 Beta ISO does not seem to recognize existing Fedora 10 system for an upgrade. (and tries to install fresh) Version-Release number of selected component (if applicable): Fedora 11 Beta DVD ISO (x86_64) How reproducible: 100% Steps to Reproduce: 1. Boot off ISO, select Install or Upgrade. 2. Walk through a few Anaconda screens until it becomes apparent we're heading for a fresh install, not an upgrade. Actual results: Landed at the partitioning screen with a default selection of "replace existing Linux system", saw no opportunity to specify an upgrade explicitly. Expected results: Upgrade existing install. Additional info: Mentioned quickly in #fedora-qa and was told it sounded like Anaconda didn't recognize my pre-existing install. Not sure if this is because of how I do my disk partitions, my layout is something like this: Device Boot Start End Blocks Id System /dev/sda1 * 1 25 200781 83 Linux /dev/sda2 26 77825 624928500 8e Linux LVM /dev/sda1 is mounted as /boot, and that LVM partition boils down to something like: $ ls /dev/vg0 blerg2@ centos-client@ centossw@ fedora@ home@ lotus@ pgsql@ rawhide@ rhel5@ root@ swap@ ubuntu@ var@ xp@ Where only home, root, swap, and var are used by the host OS, the others are for KVM guests. May not be able to test a fix if I get anxious and find another way to upgrade, but trying to hold off for now. :)
Can you attach /tmp/anaconda.log and /tmp/storage.log to this bug report? Please let anaconda run to the screens where it starts asking about timezone, root password, etc. as that will be after the existing installation detection. Thanks.
Very sorry I went ahead with a fresh install. It's a little rocky and may not be sufficient for my needs though, if it gets bad I will re-install F10 tonight and can then re-test this and submit those files. Sorry!
Feel free to reopen this bug if you do another upgrade and are able to reproduce this issue, then.
Bah, went back to Fedora 10, virtually identical partition layout, tried the ISO again, now it offers me a chance to upgrade. Not sure what the problem was.
This may have been the udev timeout problem we've seen sporadically (bug 492049), which manifests as devices and filesystems not getting recognized.