Bug 887494

Summary: Upgrade from f16 -> 17 doesn't find f16 storage
Product: [Fedora] Fedora Reporter: Sandro <spoppi>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, spoppi, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-22 20:50:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda logfile after upgrade stops
none
storage logfile after upgrade stops none

Description Sandro 2012-12-15 16:42:49 UTC
Created attachment 664039 [details]
anaconda logfile after upgrade stops

Description of problem:
Trying to upgrade from fedora 16 to 17 via preupgrade or DVD. The installer does not find the "old" f16 installation stating that the installation is "too old". On console 3 (Alt-F3) it states that /dev/loop1 cannot be accessed or /mnt/sysimage is busy.

Version-Release number of selected component (if applicable):
F17 DVD or preupgrade

How reproducible:
always

Steps to Reproduce:
1. Boot via f17 DVD or preupgrade
2. choose Install or upgrade
3. Wait until "Examining Storage" finishes
  
Actual results:
Cannot upgrade

Expected results:
Upgrade to F17

Additional info:
see anaconda and storage logs attached

Comment 1 Sandro 2012-12-15 16:43:23 UTC
Created attachment 664040 [details]
storage logfile after upgrade stops

Comment 2 Sandro 2012-12-22 20:50:25 UTC
Hi,

Found the solution in https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=835704.

Thanks,
Sandro

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