Description of problem:
Anaconda does not let me select whether I want to install new, or upgrade existing. It only presents me with the option to pick basic or advanced storage devices. When I select basic, I am only shown a list of hard drives (all 15 are detected). The advanced mode shows nothing but the hard drives. Proceeding on either path takes me down the "install new" path, and not the upgrade path. The F12 installer 'does the right thing' and prompts me to select "install new" or "upgrade existing".
Additionally, the "install new" path does not offer any of the existing LVM volumes as targets.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure existing system with mdraid and LVM
2. Boot F13 RC3 DVD and select the install or upgrade option
3. Follow the only paths available
Only taken down the "install new" path.
Offered the option to upgrade existing. Should also give the option to install new to existing LVM volumes.
Just for fun, I selected the rescue option from the DVD grub menu. It managed to find and mount all of the volumes correctly.
While anaconda was running, I got a prompt via alt-f2 and 'cat /proc/mdstat' showed no raid volumes. I then ran 'mdadm -As --auto=yes --run', 'lvm pvscan', 'lvm vgscan', and 'lvm vgchange -ay'. All of my volumes were detected and activated.
When I went back to anaconda, it listed each LVM volume as "Unknown" with the correct disk space. But again, this would be for the "install new" path.
Interestingly, when I did get all my volumes mounted, the minors for my md devices were strange. They were 123 through 127 instead of 0-4. I verified via 'mdadm --detail' that preferred minors were those numbers. When I booted F10 they were back to 0-4 and the preferred minor values were back to 0-4.
Created attachment 414397 [details]
Created attachment 414398 [details]
Created attachment 414399 [details]
The initial disk selection UI is what we call the filter UI, it is meant to filter out disks which you absolutely do not want the installer to touch at all (including not bringing up mdraid / lvm on those disks or looking there for an older version to upgrade).
As such it only shows disks (or firmware RAID sets) pure software RAID and LVM is not shown there. As rescue mode works, if you simply select all your disks there and continue you should get the upgrade / install question.
If that does not work please reopen this bug.
Created attachment 414561 [details]
New storage log which shows upgrade path being rejected
I uploaded a new storage.log which shows the following:
"product Fedora version 10 found on Raid-Root is not upgradable"
Q1: Is upgrading from F10 -> F13 truly not possible/legal?
Q2: Shouldn't the UI inform the user that one or more upgrade possibility was disallowed? Instead, I was just presented with the new install screens.
> Q1: Is upgrading from F10 -> F13 truly not possible/legal?
That is correct. Fedora only supports upgrading from n to n+1.
> Q2: Shouldn't the UI inform the user that one or more upgrade possibility was
> disallowed? Instead, I was just presented with the new install screens.
Yeah if we find older releases on the system, we should probably stop and warn about it instead of blindly moving ahead with the install. Note that this won't catch all cases, as if you have an installation we somehow cannot detect, we won't have any information to go on for presenting a warning dialog.
I'm retitling this bug to match Q2.
Fixed with commit 1dd823a0753f9d6998fc2d7db1ab4416f486ef89