Bug 541990

Summary:	Pop-up that says, Unable to mount [nfs4] filesystem during install
Product:	[Fedora] Fedora	Reporter:	Dennis Flaherty <dennisf>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	12	CC:	anaconda-maint-list, hdegoede, jvonau3, 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-11-30 09:14:22 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:

Description Dennis Flaherty 2009-11-27 20:45:40 UTC

Description of problem:

Pop-up that says, Unable to mount [nfs4] filesystem during install

Version-Release number of selected component (if applicable):
Using Anaconda to upgrade F11 to F12.

How reproducible:

Failed each time until I commented out the nfs4 service mount points in /etc/fstab.

Steps to Reproduce:

1. Have NFS4 service mount points in /etc/fstab
2. Upgrade to F12.
3.

Actual results:

Right after choosing the F11 partition to upgrade, saw a pop-up what said,

Unable to mount filesystem

An error occurred mounting device /mnt/sysimag/home as /nfs4/home:
device /mnt/sysimag/home does not exist. This is a fatal error and
the install cannot continue.

Expected results:

We can explore this in ways:
1. sysimage is misspelled as sysimag.
2. Anaconda should not try to mount my nfs4 service mount points.

While this pop-up window was displayed, I looked on another console and noticed that my F11 root was mounted on /mnt/sysimage, not /mnt/sysimag. This is probably just a misspelling in a script.

But why is Anaconda even trying? Yes, I have NFS4 mount points in my /etc/fstab:
/home /nfs4/home none bind 0 0
/usr/local /nfs4/local none bind 0 0
These are standard nfs4 service mount points that allow nfs4 clients to mount my /home and /usr/local directories.

Additional info:

I edited my fstab (in /mnt/sysimage/etc of course) to comment the lines out and tried again. It worked; I'm now running F12.

Well not completely right; I'm going to log the problem I had in the end in another bug.

-Quip11

Comment 1 Jerry Vonau 2009-11-28 18:41:50 UTC

This looks to be a dup of 541473

Comment 2 Dennis Flaherty 2009-11-29 04:54:57 UTC

That appears reasonable for the misspelling.  I'm still curious though, why even try to mount the bind points?  They only exist to allow nfs4 clients to connect to my server.

-Q

Comment 3 Hans de Goede 2009-11-30 09:14:22 UTC

The misspelling indeed seems to be a duplicate of bug 541473.

(In reply to comment #2)
> That appears reasonable for the misspelling.  I'm still curious though, why
> even try to mount the bind points?  They only exist to allow nfs4 clients to
> connect to my server.
> 

Because we do not know that, when doing an upgrade we simply mount everything in
/etc/fstab, so that when we do the upgrade and some package installs packages to some path, they always end up in the right place. People can do very funny things,
to their system so this is the only sane way to make sure we have all storage mounted in the right place before starting to upgrade packages.

As for the failing of the mount command, that could very well be caused by bug 541473 too, or by something else. Since you've already upgraded your system we won't know as upgrading twice is not possible, so I'm going to close this a duplicate of bug 541473.

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