Bug 17326 - NFS connections between two cauldron systems at same level fail
Summary: NFS connections between two cauldron systems at same level fail
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: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-12-11 19:50 CET by Frank Griffin
Modified: 2017-05-26 14:26 CEST (History)
2 users (show)

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


Attachments

Description Frank Griffin 2015-12-11 19:50:16 CET
The current cauldron NFS supplies an /etc/nfsmount.conf with Defaultvers=4 commented out.  This causes mount.nfs to insert "vers=4.2" in the mount options, which fails even when mounting a share from another system of equal level.

Uncommenting Defaultvers causes eerything to work again.

Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-12-13 08:27:43 CET
assigning to maintainer

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

Comment 2 Frank Griffin 2016-05-15 05:44:38 CEST
Ping ?
Comment 3 Marja Van Waes 2016-05-15 09:43:39 CEST
CC'ing all packagers collectively, in case the assignee is MIA (is he?)

CC: (none) => pkg-bugs

Comment 4 Frank Griffin 2016-06-29 17:10:40 CEST
This is still happening in cauldron.
Comment 5 Guillaume Rousse 2016-07-06 20:05:44 CEST
I can't reproduce using latest 1.3.4, but I tested both client and server on the same host.
Comment 6 Guillaume Rousse 2017-05-26 12:15:01 CEST
Does it still happen ?

Keywords: (none) => NEEDINFO
Status: NEW => ASSIGNED

Comment 7 Frank Griffin 2017-05-26 14:26:37 CEST
No.  Defaultvers=4 is still commented out, but this hasn't happened for some time.

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


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