Indeed it works.
Thanks gentlemen
On Wednesday, 5 March 2014 21:24:16 UTC, Makimoto Marakatti wrote:
>
> Well that is a tip I was not expecting! :)
> will try that tomorrow at work.
>
> But if it asks you the sudo password and you need to explicitly tell
> ansible-playbook to use sudo, isnt tha
Well that is a tip I was not expecting! :)
will try that tomorrow at work.
But if it asks you the sudo password and you need to explicitly tell
ansible-playbook to use sudo, isnt that a bit counterintuitive?
Right now, it asks the sudo password, but it's not using it for anything.
What's the poi
On Wednesday, March 5, 2014 7:30:57 AM UTC-8, Makimoto Marakatti wrote:
>
> I've got
>
> ask_sudo_pass = True
>
> on ~/.ansible.cfg
>
> Both are run as the user 'ansible'.
> So I'm guessing I can rule that out?
>
No. ask_sudo_pass just tells it to ask you for the sudo password. It
doesn't
I've got
ask_sudo_pass = True
on ~/.ansible.cfg
Both are run as the user 'ansible'.
So I'm guessing I can rule that out?
On Wednesday, 5 March 2014 15:26:44 UTC, Michael DeHaan wrote:
>
> The ansible command is probably running as your username vs "ansible", do
> you need to request sudo: t
The ansible command is probably running as your username vs "ansible", do
you need to request sudo: true ?
-- Michael
On Mar 5, 2014, at 10:24 AM, Makimoto Marakatti wrote:
Hi
I'm having an issue I can't even begin to understand: I'm trying to replace
some files and I can do that without any i
Hi
I'm having an issue I can't even begin to understand: I'm trying to replace
some files and I can do that without any issue if I do that from an ad-hoc
command. But if I try to do the SAME command from a playbook, it fails.
This is ansible 1.5 on centos 6.4 on the master and centos 6.x on the
