-
Notifications
You must be signed in to change notification settings - Fork 741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minimize_access: maximum recursion depth exceeded on Ansible 2.5 #171
Comments
I just tried it on CentOS7 with Ansible 2.5 and got no errors. Can you please provide, what operating system you use and what version of this role?
We're using |
Happens on an Ubuntu 17.10 target, for example, with an Arch Linux controller. It seem to recursing repeatedly through
Having a quick look into the directory, there's a symlink |
It happens on an Ubuntu 16.04 target also (same symlink). |
I get this as well, related to the Since this seem to be a default symlink in Ubuntu 16.04, I think the role should be responsible to handle this recursive case. |
@rndmh3ro Sorry to bother, but any plan for a fix? I'm available if you need a hand to test something, thanks! |
You're not bothering @allaire! :) |
This is fixed in master now! |
@rndmh3ro Thanks Sebastian, do you know if we can expect a release on galaxy anytime soon? Have a good day ! |
OpenBSD Support
When running on ansible 2.5 I get an error in the minimize_access task when processing /usr/bin:
With the last two lines repeated until the maximum recursion depth is exceeded.
I suspect this may be due to symbolic links, according to the Ansible file module documentation the follow parameter was changed from a default of 'no' to 'yes' in 2.5. Explicitly setting it to 'no' makes the task succeed.
The text was updated successfully, but these errors were encountered: