+10, Brian Coca wrote:
try
environment: {{mysettings}}
where mysettings is a group var
On Sat, May 16, 2015 at 10:55 PM, Alex Peters alex@gmail.com
javascript: wrote:
I have a couple playbooks that apply to a number of host groups, one
group
having /sbin (among other things
I tried running this very verbose command:
ansible -vvv -m setup XXX
which caused the following to be output (among other things):
rpi2-tv.38gr.net EXEC sshpass -d6 ssh -C -tt -v -o ControlMaster=auto -o
ControlPersist=60s -o ControlPath=.../.ansible/cp/ansible-ssh-%h-%p-%r -o
I tried running this very verbose command:
ansible -vvv -m setup XXX
which caused the following to be output (among other things):
XXX EXEC sshpass -d6 ssh -C -tt -v -o ControlMaster=auto -o
ControlPersist=60s -o ControlPath=.../.ansible/cp/ansible-ssh-%h-%p-%r -o
GSSAPIAuthentication=no -o
I hate bumping my own posts without contributing any more information, but
I'm totally stuck on this issue and I can't progress without assistance.
Can someone please provide me with some more direction towards resolving
this problem?
--
You received this message because you are subscribed to
On Tuesday, 12 May 2015 00:29:42 UTC+10, Marcus Franke wrote:
if you are looking for problems with sudo you can login as your ansible
user and issue sudo -l. This will list all commands your ansible user is
allowed to use.
The output of this command on the affected machine is as follows:
$
I've been unable to resolve this issue with the ideas presented so far. In
the absence of any further responses, should I consider this an Ansible bug
and file a bug report?
On Sat, 9 May 2015 at 22:18 Alex Peters alex.pet...@gmail.com wrote:
On Friday, 8 May 2015 23:55:32 UTC+10, Brian Coca
Would giving you SSH access to this particular machine be useful?
On Mon, 11 May 2015 11:53 pm Brian Coca bc...@ansible.com wrote:
i'm unable to reproduce the issue, the path seems fine, not sure if
its a bug or not, but without a way to reproduce the issue I'm not
sure how it will get
On Friday, 8 May 2015 23:55:32 UTC+10, Brian Coca wrote:
try: sudo sh -c 'echo $PATH'
su can readd path info, the above is closer to what ansible does (it
uses sudo -u user not sudo su).
Done:
$ sudo sh -c 'echo $PATH'
On Fri, 8 May 2015 11:55 pm Brian Coca bc...@ansible.com wrote:
try: sudo sh -c 'echo $PATH'
su can readd path info, the above is closer to what ansible does (it
uses sudo -u user not sudo su).
$ sudo sh -c 'echo $PATH'
On Tuesday, 5 May 2015 01:21:17 UTC+10, Brian Coca wrote:
When you gather facts on the machine, you should be able to see the
'PATH' that ansible sees under ansible_env, ansible uses it's own path
list to find apt and dpkg, but that should not influence the other
tools, which ansible is
I'm trying to install a package on a system running a Debian Jessie-based
distribution called OSMC https://osmc.tv/.
This task (run with ansible_sudo == true):
- name: ensure Vim is installed
apt: name=vim state=present
causes this to happen:
TASK: [vim | ensure Vim is installed]
11 matches
Mail list logo
