Hi Paul,
Anything I can do to help with this? I am starting a sprint next week and
will be feeling the pain if I can't use ansible to support our work. I am
happy to try and find the issue in source, not so happy to try and edit
Python code. I didn't want to duplicate work if you were
Hi Michael,
I posted about a problem using copy and template module with su on Apr 29th
with ansible 1.6.
I probably posted it wrong, I don't get out much.
Should I have replied to the last message in the thread instead of the
first? I also wondered if it was ok to leave all the original quote
Thanks for any help you can give. Let me know if you need any more info.
I also see it happening in the template module:
{msg: Could not replace file:
/tmp/.ansible/tmp/ansible-tmp-1398978322.77-92955034866020/source to
Thanks for this feature, I absolutely need it. I do seem to have an issue
using it.
I am using ansible 1.6 (devel eb090ad4a2) on RHEL 6. When I use su with
the copy module I get a permission denied error.
I use a remote user to login to the server then su to another acccount.
This is
I'm looking at this as well, and believe that I may have identified and fixed
the issue. I'm going to talk it over with Paul (angstwad) for validation and
testing.
--
Matt Martz
m...@sivel.net
On January 23, 2014 at 9:37:01 PM, James Tanner (tanner...@gmail.com) wrote:
On 01/23/2014 08:38
The following playbook doesn't do what I think it should. The su on the
task stays as root.
I was asked to file a bug; I could still do so. But if you think you
have a handle on it, then it might just be better to past this here.
cmd: ansible-playbook -i hosts.txt su-for-task-broken.yml
Adam,
See the pull request that was just submitted:
https://github.com/ansible/ansible/pull/5751
That should resolve your issue. If you are up to testing it, please do so and
let us know if it resolves your issue.
--
Matt Martz
m...@sivel.net
On January 24, 2014 at 11:31:29 AM, Adam Heath
Hi Adam,
Thanks for reporting this. I submitted a PR this morning based on your
issue.
https://github.com/ansible/ansible/pull/5751
On Friday, January 24, 2014 11:24:23 AM UTC-6, Adam Heath wrote:
The following playbook doesn't do what I think it should. The su on the
task stays as
This doesn't work with the git module. If I use sudo:true and sudo_user:
{{item.owner}, then the git module does the correct thing. However, If I
do su:true and su_user: {{item.owner}}, then the git module continues to
run as root(I am connecting remotely as root for my playbook).
I haven't
On 01/23/2014 08:38 PM, a...@brainfood.com wrote:
This doesn't work with the git module. If I use sudo:true and
sudo_user: {{item.owner}, then the git module does the correct thing.
However, If I do su:true and su_user: {{item.owner}}, then the git
module continues to run as root(I am
10 matches
Mail list logo
