FIX nfs4acl default flag not working #636
Draft
Conversation
This file contains hidden or 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
… ACL processing currently not working is the indempodency, so the permissions are getting set every time when executet
|
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 18s |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
SUMMARY
Currently the default flag for nfs4_acl is not working propably and giving back an invalid option message. This should Fixes #625
ISSUE TYPE
COMPONENT NAME
acl
ADDITIONAL INFORMATION
I was able to fix the option flag and that it is working now. But currently the indempodency is not working and executes the commands every time and gives back an ansible changed something information and the command output for setting the option is giving back an "permission is already set"