Bug 817041
Summary: | rpc.idmapd not started on client | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> |
Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | bfields, jlayton, matt, ndevos, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-17 20:43:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Richard W.M. Jones
2012-04-27 13:50:07 UTC
The workaround I've been using is systemctl enable nfs-server.service on the client. I only need the client to be the "client" but that service starts idmapd so meh What kernel version are you using? With 3.3 and beyond the idmapped was changed to use a keyring based idmapping using the nfsidmap command. See nfsidmap(5) for details. With the being the cause the rpc.idmapd daemon no longer needed to be started on the NFS client. Interesting ... This is arm, so it was: Linux trim.home.annexia.org 2.6.41.7-1.0.arm1.y1.armv7hl.tegra #1 SMP PREEMPT Fri Jan 20 11:31:29 EST 2012 armv7l armv7l armv7l GNU/Linux because there *was* a problem booting this hardware with the newer kernel. Since (even) newer kernels are available I need to try those. I'll try to reboot this machine later today (currently it's running some crucial builds). Yes, confirmed that this does work with the later kernel. |