This repository has been archived by the owner on Mar 8, 2023. It is now read-only.
Enable idmapd service on Ubuntu when NFSv4 configured; disable when not. #54
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Backmerge Develop for release 1.7.0
merge develop branch for 1.7.1
If the idmapd service is disabled, make sure it is enabled on Ubuntu if NFSv4 is configured. Also make sure that it is disabled if NFSv4 is not configured otherwise it would start on boot.
|
Thanks for the PR. Would you like to add teh same change for debian too? Would be nice. |
|
My fault. Debian dont have this service issue. |
dwerder
added a commit
that referenced
this pull request
Jan 7, 2016
Enable idmapd service on Ubuntu when NFSv4 configured; disable when not.
|
No problem. I thought I checked all of the services but missed that Debian one for some reason.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the case of $nfs::client::ubuntu::nfs_v4 = false, Puppet would stop the idmapd service but when the host is rebooted, the service will start again as it wasn't disabled. The inverse is also true for $nfs::client::ubuntu::nfs_v4 = true. This caused puppet to make a change on the first run after every reboot. Adding the enable parameter to the service resources should fix this.