Updated on this:
This problem occurred if I set connection: local in playbook, I often use
it when running local playbook from command line, if remove that line the
playbook runs successfully from Ansible Tower.
So question: Doesn't Ansible Tower run playbook with 'local' connection? As
in the case run local playbook from Ansible Tower I still need to provide
credentials.
On Wednesday, 29 July 2015 11:18:43 UTC+7, Do Hoang Khiem wrote:
>
> I've deployed an instance of Ansible Tower (using official Ansible EC2
> AMI) on one of our server. There're some of our playbooks that always run
> locally (so, hosts = localhost, connection = local). Normally those
> playbooks run fine when run with ansible-playbook from command line but I
> always got this error when run the same playbook from Ansible Tower job
>
> failed: [localhost] => (item=git,ruby,npm,nodejs-legacy) => {"failed":
> true, "item": "git,ruby,npm,nodejs-legacy", "parsed": false} sudo:
> effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid'
> option set or an NFS file system without root privileges?
>
> the task is a simple apt
>
> - name: "ensure required packages: git, ruby, npm and nodejs-legacy are
> installed"
> apt: pkg={{item}} state=installed force=yes
> with_items:
> - git
> - ruby
> - npm
> - nodejs-legacy
> sudo: yes
>
> Another thing I don't know is whether run playbook from Ansible Tower with
> connection=local like with ansible-playbook? As with ansible-playbook when
> running on localhost and connection=local I don't need credentials while
> with Ansible Tower currently I have to provide credentials (SSH key) for
> localhost access.
>
> Thanks in advance for any comments!
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/ba9c79d4-4735-48bd-9053-05dc849c2f13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
