Bug 682047 - F14 install not detected by F15 Install
Summary: F14 install not detected by F15 Install
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-04 01:29 UTC by Brian Lane
Modified: 2011-03-04 17:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-04 17:50:03 UTC
Type: ---


Attachments (Terms of Use)
anaconda.log (6.49 KB, text/plain)
2011-03-04 01:30 UTC, Brian Lane
no flags Details
ifcfg.log (510 bytes, text/plain)
2011-03-04 01:30 UTC, Brian Lane
no flags Details
program.log (8.13 KB, text/plain)
2011-03-04 01:30 UTC, Brian Lane
no flags Details
storage.log (124.96 KB, text/plain)
2011-03-04 01:31 UTC, Brian Lane
no flags Details
syslog (45.31 KB, text/plain)
2011-03-04 01:32 UTC, Brian Lane
no flags Details
X.log (25.08 KB, text/plain)
2011-03-04 01:32 UTC, Brian Lane
no flags Details

Description Brian Lane 2011-03-04 01:29:32 UTC
F14 minimal system

/boot on a RAID1
/ and swap in a PV on top of another RAID1

After examining storage Fedora15 doesn't offer to upgrade the install.

Comment 1 Brian Lane 2011-03-04 01:30:06 UTC
Created attachment 482191 [details]
anaconda.log

Comment 2 Brian Lane 2011-03-04 01:30:29 UTC
Created attachment 482192 [details]
ifcfg.log

Comment 3 Brian Lane 2011-03-04 01:30:55 UTC
Created attachment 482193 [details]
program.log

Comment 4 Brian Lane 2011-03-04 01:31:46 UTC
Created attachment 482194 [details]
storage.log

Comment 5 Brian Lane 2011-03-04 01:32:36 UTC
Created attachment 482196 [details]
syslog

Comment 6 Brian Lane 2011-03-04 01:32:59 UTC
Created attachment 482197 [details]
X.log

Comment 7 Brian Lane 2011-03-04 17:50:03 UTC
dlehman's updates.img from https://bugzilla.redhat.com/show_bug.cgi?id=681608#c13


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