Bug 496406

Summary: Anaconda barfs on bind mount in fstab
Product: [Fedora] Fedora Reporter: Callum Lerwick <seg>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: chris, dlehman, eric.moret, mnaysmit, pjones, rmaximo, seg, vanmeeuwen+fedora, victorgubin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:a405b99573650322975b1bf13f75c2f5e51f0d62735b027339b0d839272ff305
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 494992 Environment:
Last Closed: 2009-07-17 16:20:47 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:
Bug Depends On: 494992    
Bug Blocks:    
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description Callum Lerwick 2009-04-18 18:29:54 UTC
+++ This bug was initially created as a clone of Bug #494992 +++

Anaconda is harfing on a bind mount now. See bz #494992 for traceback.

Comment 1 David Lehman 2009-04-30 23:04:14 UTC
This should work correctly as of anaconda-11.5.0.48-1. Actually, the change I made there may have introduced a different bug which will be cleared up in anaconda-11.5.0.49-1, which has not yet been built.

Comment 2 Bug Zapper 2009-06-09 14:05:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Chris Paulson-Ellis 2009-06-11 20:36:11 UTC
Created attachment 347470 [details]
Attached traceback automatically from anaconda.

Comment 4 Chris Paulson-Ellis 2009-06-11 20:46:41 UTC
Anaconda decided to attach its traceback to this bug.

My problem was caused not by a bind mount fstab entry, but by a davfs2 entry like this one (details changed, but syntactically the same):

https://server.example.com:1234/share/ /mnt/share davfs noauto,user 0 0

I was upgrading from F10 to F11, via preupgrade.

Comment 5 Matthew 2009-06-15 02:27:31 UTC
Created attachment 347883 [details]
Attached traceback automatically from anaconda.

Comment 6 Eric Moret 2009-06-15 22:06:06 UTC
Created attachment 348018 [details]
Attached traceback automatically from anaconda.

Comment 7 Eric Moret 2009-06-15 22:15:07 UTC
Following an attempt to upgrade from Fedora 10 to Fedora 11 with preupgrade I saw an anaconda crash (See Commend #6) due to the following lines in my /etc/fstab

[...]
# Begining of the block added by the VMware software
.host:/                 /mnt/hgfs                 vmhgfs   defaults,ttl=5   0 0
# End of the block added by the VMware software

Comment 8 Matthew 2009-06-16 01:34:10 UTC
Same issue for me, just had to comment the .host:/ line in /etc/fstab and all was OK

Comment 9 David Lehman 2009-06-17 17:04:26 UTC
(In reply to comment #7)
> Following an attempt to upgrade from Fedora 10 to Fedora 11 with preupgrade I
> saw an anaconda crash (See Commend #6) due to the following lines in my
> /etc/fstab
> 
> [...]
> # Begining of the block added by the VMware software
> .host:/                 /mnt/hgfs                 vmhgfs   defaults,ttl=5   0 0
> # End of the block added by the VMware software  

This should be fixed by commit 2d1560fb8e92ff4a01ee8ba48069475e274fc954 to anaconda. The same commit should fix the failure with the davfs line as well.

Comment 10 Victor Gubin 2009-07-15 17:22:10 UTC
Created attachment 353855 [details]
Attached traceback automatically from anaconda.

Comment 11 Callum Lerwick 2009-07-16 16:57:38 UTC
Note that I stripped my fstab bare and had no further problems pre-upgrading to F11 some time ago. So I won't be doing any further testing of this bug. If you believe that it is fixed, feel free to close the bug.

Comment 12 David Lehman 2009-07-17 16:20:47 UTC
This bug should be completely resolved in anaconda-12.0-1. Please reopen if you find the issue persists.