Bug 508932

Summary: anaconda misparses bind mounts
Product: [Fedora] Fedora Reporter: Ralf Corsepius <rc040203>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 11CC: anaconda-maint-list, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-30 15:22:55 UTC Type: ---
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
Photo of screen, from a failing "upgrade" none

Description Ralf Corsepius 2009-06-30 15:14:26 UTC
Description of problem:

anaconda, as on the F11-CDs/DVDs, is unable to parse bind-mounts from fstab.
Instead of correctly processing them, it fails badly and aborts.

This significantly reduces usability of the CDs/DVDs for upgrading existing installations and using the F11-CDs/DVD's "rescue mode".


Version-Release number of selected component (if applicable):
anaconda-11.5.0.59-1.fc11.x86_64

How reproducible:
Always

Steps to Reproduce:
1. On an FC10 system, add a "bind" mount to /etc/fstab
E.g.
...
/dev/VolGroup01/LogVol02 /home         ext3    defaults        1 2
/home/ftp/pub  /var/ftp/pub            none    bind
..

2. Reboot with F11 DVDs

Alternative: Add bind-mounts to /etc/fstab and try to boot from DVD in "rescue mode".


Actual results:
"upgrading" or "rescue installed system" aborts with:

"An error occurred mounting device /mnt/sysimage/home/home/ftp/pub as /var/ftp/pub: device /mnt/sysimage/home/home/ftp/pub does not exist"

(Note the duplicate /home)

Expected results:
Function.

Comment 1 Ralf Corsepius 2009-06-30 15:16:42 UTC
Created attachment 349961 [details]
Photo of screen, from a failing "upgrade"

Comment 2 Chris Lumens 2009-06-30 15:22:55 UTC

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