Bug 17327 - New NFS deletes existing /etc/exports
Summary: New NFS deletes existing /etc/exports
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-11 19:58 CET by Frank Griffin
Modified: 2015-12-22 20:42 CET (History)
1 user (show)

See Also:
Source RPM: nfs-utils
CVE:
Status comment:


Attachments

Description Frank Griffin 2015-12-11 19:58:19 CET
On two separate cauldron systems I have found that my custom /etc/exports files have been deleted.  This isn't apparent unless nfs-server is restarted or the system is rebooted.  I assume this is caused by the same nfs-server upgrade that caused vers=4.2 mounts to fail ( bug#17326 ).  Not nice.

Reproducible: 

Steps to Reproduce:
Marja Van Waes 2015-12-13 08:29:17 CET

CC: (none) => marja11
Assignee: bugsquad => guillomovitch
Source RPM: nfs => nfs-utils

Comment 1 Guillaume Rousse 2015-12-13 20:22:36 CET
This file doesn't exist anymore in the package, as it seems to have been superceded by /etc/exports.d directory. As it is marked as a configuration file, it should not have been deleted, but rather renamed to /etc/exports.rpmsave.
Comment 2 Frank Griffin 2015-12-14 02:09:45 CET
You're right.  It was renamed to /etc/exports.rpmsave.  So far, so good.

However, when I recreated /etc/exports, things worked again, so the package will still apparently use /etc/exports if it's there.

That being the case, I would expect that rather than renaming the file and leaving nothing in its place, it would get replaced with a dummy file containing a comment describing the change and pointing to /etc/exports.d/.

If I'm off-base here, you can just close this as INVALID.
Comment 3 Guillaume Rousse 2015-12-22 20:42:22 CET
Fixed in nfs-utils-1.3.3-2.mga6.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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