Hi,
my two cents would be:
1. Make sure you use absolute paths when invoking the "apt-get update"
and "apt-get install" commands (*whereis apt-get* helps here...)
2. Make sure you use the "shell" module instead of the "command" module
since the shell module allows redirection and pipe and that kind of stuff
Cheers
Ralph
Am Dienstag, 29. April 2014 05:11:01 UTC+2 schrieb Gallagher Polyn:
>
> Hi,
>
> Having just provisioned a Digital Ocean droplet, in my next pre_task, I
> proceed to attempt to upgrade apt packages:
>
> apt: upgrade=full update_cache=yes
>
>
> ...using this command form...
>
> ansible-playbook -i hosts basic.yml -vvvv
>
>
> ...I obtain the following error:
>
> failed: [127.0.0.1] => {"cmd": "apt-get update && apt-get install
> python-apt -y -q", "failed": true, "rc": 127}
> stderr: /bin/sh: apt-get: command not found
> msg: /bin/sh: apt-get: command not found
>
>
> Shelling into the newly-provisioned droplet as root, however, I am able to
> execute apt-get update normally.
>
> Any thoughts?
>
> Thanks,
>
> Gallagher
>
--
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/88233a37-8962-4ac1-b626-497825be6599%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
