://groups.google.com/d/msgid/ansible-project/aaf25e0e-0210-4ab7-bb45-16835e26f824%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
Steven Haddox
http://stevenhaddox.com
--
You received this message because you
Simple code below has been working for about a week, randomly at work (and
now at home) I've been getting the following error. Originally the
commented line was present and produced the following error, but the below
error may be the bigger culprit:
Code being executed:
# Detect apr
-
If it helps at all I've updated the Gist to include an example of a
non-root user via sudo with the raw module that works for comparison as
well:
https://gist.github.com/stevenhaddox/d497727deffa65b1a5e1
So... logging in and running modules directly as myself works, and via sudo
to a non-root
each upload
or if there's even a way I can upload the modules myself and change the
permissions on them and have ansible use the pre-uploaded modules somehow?
Thanks again,
Steven
On Thursday, December 12, 2013 11:47:46 AM UTC-5, Steven Haddox wrote:
Due to the joys of Enterprise security
This is ansible 1.4.1
My user authenticates via key-based SSH connection without a password.
On Thursday, December 12, 2013 11:55:15 AM UTC-5, Brian Coca wrote:
A fix was added to explicitly chmod the file when using sudo to a non root
user, check version, this should be fix in current
Due to the joys of Enterprise security, it appears that ansible is hanging
(literally just sits until I Ctl+C like 10 minutes later) when trying to
run any modules besides raw.
So for an example of a working command:
$ ansible all -i path/to/hosts_file -m raw -a whoami; hostname -u
myself -s
-Steven
On Thursday, December 12, 2013 11:57:01 AM UTC-5, Steven Haddox wrote:
This is ansible 1.4.1
My user authenticates via key-based SSH connection without a password.
On Thursday, December 12, 2013 11:55:15 AM UTC-5, Brian Coca wrote:
A fix was added to explicitly chmod the file when
being called via system python directly so it really shouldn't have).
Now I have no clue why it's just hanging after being invoked...
On Thursday, December 12, 2013 12:06:32 PM UTC-5, Steven Haddox wrote:
It also appears to run properly when I run:
$ python /tmp/ansible-/command
So oddly it's
was able to see
it's being called via system python directly so it really shouldn't have).
Now I have no clue why it's just hanging after being invoked...
On Thursday, December 12, 2013 12:06:32 PM UTC-5, Steven Haddox wrote:
It also appears to run properly when I run:
$ python /tmp
Alright, here goes nothing. I had to retype this by hand so forgive any
typos...
https://gist.github.com/stevenhaddox/d497727deffa65b1a5e1
Thanks for any ideas,
Steven
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from
Sorry, the shell action line should read:
shell: bash ( curl {{rvm_fw_url}}/releases/rvm-install-latest )
I tried to escape it as a debug measure with no success.
Thanks!
On Friday, November 29, 2013 6:27:46 PM UTC-5, Steven Haddox wrote:
I'm trying to run a task that invokes bash as part
, 2013 at 7:02 PM, Steven Haddox ste...@haddox.usjavascript:
wrote:
Sorry, both the control machine (my MacBook Air) and the Ansible remote
node (my vagrant VM) are running perfectly fine (I can ssh into the Vagrant
VM without a problem, and Ansible eventually does run through the play book
Michel,
It's definitely not the way old school RVM instructions said it had to be
done, but it seems to work on this particular instance just fine!
Thanks!
On Friday, November 29, 2013 6:53:56 PM UTC-5, Michel Blanc wrote:
On 30/11/2013 00:29, Steven Haddox wrote:
Sorry, the shell action
When I'm trying to develop my play books while offline on my laptop (using
vagrant for my Ansible provisioned server) I'm seeing really long hangs on the
GATHERING FACTS task (as in the order of 3-5 minutes). After it eventually
times out (best guess) it proceeds as normal and everything works
Sorry, both the control machine (my MacBook Air) and the Ansible remote node
(my vagrant VM) are running perfectly fine (I can ssh into the Vagrant VM
without a problem, and Ansible eventually does run through the play book after
the 3-5 minutes pause on gathering facts completes. The only
Ordered. This is awesome. Thanks for giving us a chance to share the love 3
On Monday, November 18, 2013 2:01:33 PM UTC-5, Michael DeHaan wrote:
Hi everyone,
Several people approached us about wanting to get a copy of the flying
computer shirt we were giving away at AWS re:Invent.
As we
16 matches
Mail list logo
