So, I found the problem. Actually, I'm not sure if it's a problem or
desired behaviour :)
When I run 'source hacking/env-setup', the PYTHONPATH environmental
variable gets set to the 'lib' directory in the ansible repository used for
development. This directory however does not contain the
So, I found the problem. Actually, I'm not sure if it's a problem or
desired behaviour :)
When I run 'source hacking/env-setup', the PYTHONPATH environmental
variable gets set to the 'lib' directory in the ansible repository used for
development. This directory however does not contain the
Hi,
I would like to restart a server and wait till the services start up. I can
us the wait_for module to wait for ports to be up, but how can I wait for
the services to be up? The service modules seem to start,stop or restart
service, but I don't want to do any of these operations. Only wait
Hi i am connecting to my ec2 instance and i am getting this error , please
help
ssh centos@10.103.1.235 -vvv
OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /root/.ssh/config
debug1: /root/.ssh/config line 1: Applying options for 10.103*
debug1: Reading
We're just using the stock ec2 and ubuntu mirrors. Running apt directly on
the cli has no issues.
On Friday, December 2, 2016 at 7:54:23 PM UTC-8, Andreas Olsson wrote:
>
> fre 2016-12-02 klockan 15:16 -0800 skrev ja...@blendlabs.com :
>
> > {"failed": true, "invocation": {"module_args":
Hi,
this inventory script can be useful if you use Vagrant:
https://github.com/harobed/ansible-dynamic-vagrant-inventory
Best regards,
Stéphane
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop
>From the ticket, looks like a simple perms issue -- but I would like
to hear if anyone else is experiencing this.
On Mon, Dec 5, 2016 at 11:28 AM, 'Chris Short' via Ansible Project
wrote:
> I've filed a ticket on this but there does not seem to be a workaround
I've filed a ticket on this but there does not seem to be a workaround
(https://github.com/ansible/galaxy-issues/issues/217). I wrote a role that
I want to deploy to Galaxy but the GitHub integration fails to work every
time. Has anyone experienced this and is there a fix?
--
You received
Bump!!
There is got to be some trick involved but i can't think of any.
On Wednesday, 30 November 2016 13:30:01 UTC+1, ishan jain wrote:
>
> I have a number of playbooks each related to starting a container for a
> microservice using docker_container module. I supply the variables like
> image
Also tested on a bare metal Solaris 8 machine, and it has the same
problems, so it does not seem to be related to the zones.
Maybe I should file a proper bug report, but since I´m new to Ansible I
want to rule out my incompetence as the cause first.
On Tuesday, November 29, 2016 at 7:31:26 PM
OK, so I looked at Ansible's code, and I now know how to implement this.
I tried my modification locally and
it works fine. It basically adds a module that adds an 'extra_vars'
variable if it does not yet exist.
That way, any variable set on the commandline using the '--extra-vars'
Hi
My requirement is to install multiple patches on different
machines based on which all tiers the patch is supported for install. Say
patch1 should be installed on client group and service group, patch2 should
be installed on client group and database group machines.
- name:
12 matches
Mail list logo