Bug 499407 - Preupgrade from F10 to F11 preview (Rawhide) fails if you have encrypted disk.
Summary: Preupgrade from F10 to F11 preview (Rawhide) fails if you have encrypted disk.
Keywords:
Status: CLOSED DUPLICATE of bug 499321
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-06 15:00 UTC by Sirius Rayner-Karlsson
Modified: 2009-05-06 15:03 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-06 15:03:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
textfile collected from the upgrade process after failing (76.49 KB, text/plain)
2009-05-06 15:00 UTC, Sirius Rayner-Karlsson
no flags Details

Description Sirius Rayner-Karlsson 2009-05-06 15:00:53 UTC
Created attachment 342670 [details]
textfile collected from the upgrade process after failing

Description of problem:

I decided to preupgrade to F11 Preview today. Everything went great until I rebooted in to the installer and it attempted to find my rootfs. It bailed out, saying it could not find the rootfs. Attaching the log I collected.

Version-Release number of selected component (if applicable):
11.5.0.49

How reproducible:
100%

Steps to Reproduce:
1. Install F10, electing to encrypt disk
2. update to latest (I've got updates-testing enabled too)
3. preupgrade to F11 Preview (Rawhide)
  
Actual results:
After reboot to complete the upgrade, the installed stops on not finding the rootfs.

Expected results:
Updated system.

Additional info:
I did have some packages with unresolved dependencies, but due to where the upgrade failed, I doubt they are relevant (some php5, midgard and internal tools)

Comment 1 Chris Lumens 2009-05-06 15:03:53 UTC

*** This bug has been marked as a duplicate of bug 499321 ***


Note You need to log in before you can comment on or make changes to this bug.