-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
msg: Failed to change ownership of the temporary files Ansible (via chmod nor setfacl) needs to create … #1
Comments
Huh. Ran into this again, in an unrelated situation, two months later. Same error, basically; again with
This is confusing, because the README says:
|
Just to call attention to it, it looks like some err: chmod: invalid mode: ‘A+user:{{ ansible_user if ansible_os_family == 'Windows' else omit }}:rx:allow’ |
Also, it tries to pass the same argument to
|
Hi Guys, Solution applied in 'execution-environment.yml' Since it is Windows access, the user is Administrator or another windows account (no exist in EE container), If you activate the debugging level 5 (winrm), you will notice a setfacl message passing the Administrator user, as it is localhost (delegate_to: localhost), this user does not exist in podman. append in file: execution-environment.yml additional_build_steps: |
❔ What are you experiencing an issue with?
Latest Release
❔ Version
v2.3.0
🐞 Description
Attempting to run the
professormanhattan.deno
role, without arguments or other roles, resulted in this error-message:… reading some docs, and doing some Googling, I tried the following:
turning on root-login, and switching my inventory to instruct the playbook to run as
root
— the error changed to this, but still occurs:Adding the
aisbergg.acl
to ensuresetfacl
exists (now it does), but still the same error;Configuring ansible to use a different
remote_tmp = /tmp/.ansible/tmp
directory, still the same error.⏺️ Steps To Reproduce
$ ansible-playbook -vvv -i hosts.yaml playbook.yaml
📒 Relevant Log Output
💡 Possible Solution
No response
The text was updated successfully, but these errors were encountered: