Bug 389851 - Upgrade to F8 fails on non-default swap location
Summary: Upgrade to F8 fails on non-default swap location
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 8
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-19 01:10 UTC by John Mellor
Modified: 2008-08-02 23:40 UTC (History)
0 users

Fixed In Version: F9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-05 00:17:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Mellor 2007-11-19 01:10:11 UTC
Description of problem:
Unable to upgrade if swap is not on VolGroup00

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


How reproducible:
unkown, I've only doen it once and had to fresh-install to work-around

Steps to Reproduce:
1.F7 installed on VolGroup07 instead of the default VolGroup00 (to work around
completely insufficient failed-disk handling in lvm and in recovery disk).
2.Install F8 in upgrade mode.
  
Actual results:
Install fails almost immediately, with an unable to find swap on VolGroup00 message.

Expected results:
Normal upgrade installation.

Additional info:

Comment 1 John Mellor 2007-11-19 01:14:52 UTC
I only installed F7 in VolGroup07 because of prior bad history of trying to
recover from a corrupted root disk by installing a second disk, and being unable
to mount the partially-failed filesystem because it was part of the same volume
group as the new root disk.  As an aside, someone, please fix the completely
broken lvm tools that do not handle this very-common scenario at all.

Comment 2 Phil Knirsch 2007-11-20 16:17:49 UTC
Reassigning to installer component (anaconda) as this is more of an installer
problem than a problem with the component setup.

Read ya, Phil

Comment 3 Andy Lindeberg 2008-06-03 18:40:44 UTC
Have you been able to reproduce the problem in F9?

Comment 4 John Mellor 2008-06-05 00:17:37 UTC
Problem does not occur in F9 fresh install.  Presumed fixed.


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