Description of problem:

(reproduced from fedora forums)

If you have dual/multiple boot Fedora installations, preupgrade/anaconda may upgrade the wrong installation!

So let's get to the story. When I first bought this computer a year and a half ago, I installed Fedora 7 onto it; a completely clean installation with nothing but Fedora 7. It was the first time I have ever installed Fedora onto my own computer. After Fedora 9 came out and support for Fedora 7 was dropped, it became clear that I needed to upgrade, but due to various issues (I had made many tweaks to my F7 installation to get everything working), I wanted to install it separately to make it dual boot 7 and 9. It was at this time I discovered the joys of LVM. To cut a long story short, I installed Fedora 9 onto a new logical volume that I created and dual booted like that. It allowed me to take my time migrating to F9. All was well.

As it happened I didn't need to make huge adjustments to F9 to get everything working, so when F10 came out I wanted to use a much easier method of upgrading, so I decided to use preupgrade <insert dramatic music here>. It was problematic. Anaconda couldn't find the preupgrade repo cache, as I talk about in this thread: http://fedoraforum.org/forum/showthread.php?t=205131.

I got around that problem as described in that post, and anaconda proceeded and all seemed well.

Until it rebooted. It froze during the boot. A little troubleshooting, and I discover that anaconda didn't upgrade the F9 partition - it "upgraded" (read "ruined") the F7 one! This was totally unexpected to me since of course I originally ran preupgrade in the F9 installation. At no stage was I ever asked to clarify where I wanted the upgrade performed.

I now suspect that the reason anaconda couldn't see the preupgrade repo cache was because it was looking in the wrong LVM volume. But as I stated in the other post, I checked the grub file and all looked well...

In the end, the F9 partition was untouched and I'm using it now with no problem. But the F7 installation is ruined. The data is easily accessible, but I suspect /etc is fried.



Version-Release number of selected component (if applicable):
Was upgrading from Fedora 9 to Fedora 10.

How reproducible:


Steps to Reproduce:
1. Freshly install Fedora onto the hard drive, allowing anaconda to set up LVM
2. Make a new LVM volume and install another copy of Fedora on that one too, making it dual boot.  (A different version would be a good idea, the second one should be the later version).
3. Use preupgrade to upgrade the second installation.
4. Upon rebooting, anaconda will fail to find the preupgrade repo cache.  Copy the cache to another location and point anaconda to it.
5. Anaconda upgrades the wrong partition.


  
Actual results:


Expected results:


Additional info: