Updated this PR, added state='allocate' option, and fixed logic that looks
for free elastic IPs that aren't currently associated with an instance.
On Tuesday, November 11, 2014 12:05:44 PM UTC-5, Herby Gillot wrote:
>
> 1) I personally think that if no public IP is specified, but an instance
> I
following up on this... is this a bug or an expected behaviour?
On Friday, November 7, 2014 9:43:45 AM UTC-5, Sean McGowan wrote:
>
>
>
> On Friday, November 7, 2014 9:25:43 AM UTC-5, Michael DeHaan wrote:
>>
>> Can you please be explicit about what the "not a very cool behavior" is ?
>>
>
> no pr
issue #302 - ansible-modules-core
thanks!
and i never expect fifo's to work, but it is a nice shortcut when testing.
:)
On Friday, November 7, 2014 9:13:33 AM UTC-5, Michael DeHaan wrote:
>
> Assuming you mean the (>$) whichever weird syntax, using fifo's as an
> inventory file was never real
I think the problem could be caused by the delegate_to
Have you tried running the playbook without it? i.e. let the Munin master
node to generate the conf file dynamically by being the one that connects
to each Munin node to fill in the template.
On Friday, 26 September 2014 13:52:13 UTC+2, Sibi
No, still skipping. But I got the answer. Check the forum
https://groups.google.com/forum/?#!topic/ansible-project/BBbdxspBzHI
2014-11-11 18:04 GMT+01:00 Petros Moisiadis :
> On 11/11/14 18:32, Petros Moisiadis wrote:
>
> On 11/11/14 18:12, cdar z wrote:
>
> Sorry, I made mistake. Bad example. I
I tried this today after rebooting XP and the timing is the same -- scp
takes < 1 sec and ansible taking 1.2 sec, as I didn't delete the already
copied file. After I deleted, ansible took 3.5 secs.
I am on Linux host and running XP on virtualbox on the same Linux host.
Any idea why ansible take
1) I personally think that if no public IP is specified, but an instance ID
is provided, then nothing should be done if that instance already has an
elastic IP attached to it.
2) If we want to simply allocate a new Elastic IP, then I agree that that
should simply be a new state flag, state='all
That's a bummer. Thank You a lot.
W dniu wtorek, 11 listopada 2014 18:01:18 UTC+1 użytkownik Michael Peters
napisał:
>
> Adding a when condition to an include doesn't conditionally include
> the file, it instead adds that condition to every task in that file.
> So in this case yes, the debug do
Adding a when condition to an include doesn't conditionally include
the file, it instead adds that condition to every task in that file.
So in this case yes, the debug does have the when statement.
On Tue, Nov 11, 2014 at 11:53 AM, cdar z wrote:
> But debug doesn't have when statement. If set_fac
I notice if multiple playbooks are applied to the same host concurrently,
ansbile will not take any lock but let they all run; this result some
playbooks fail because system conflict, for example, failing to acquire apt
lock on ubuntu. Is there any option can serialize concurrent playbooks
exec
But debug doesn't have when statement. If set_fact was runned, debug should
too.
W dniu wtorek, 11 listopada 2014 17:44:09 UTC+1 użytkownik Brian Coca
napisał:
>
> still works as expected.
>
> set fact runs when bar is not defined, debug is skipped on the same
> condition as it isn't true once
still works as expected.
set fact runs when bar is not defined, debug is skipped on the same
condition as it isn't true once set fact sets bar.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group an
Sorry, I made mistake. Bad example. I meant this one:
$ cat inv
local ansible_connection=local
$ cat extra.yml
---
- set_fact: bar=hello
- debug: msg="baz {{ bar }}"
$ cat playbook.yml
---
- hosts: local
tasks:
- include: extra.yml
when: bar is not defined
$ ansible-playbook -i inv play
cause you asked it to?
I think you want:
```
when: bar is defined
```
--
Brian Coca
--
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 ansible-project+unsubs
Also apologies, I was offline for a bit and then had other priorities at
work.
I've downloaded your github example as a zip file, unpacked it, modified
host and usernames to reflect the local situation.
I now don't get an error, but now the tasks just show "skipping" for
everything:
PLAY [Add
Never mind that erroneous include. It's now properly aligned and Ansible
doesn't get surprised anymore by what I'm including :)
On Tuesday, 11 November 2014 16:39:00 UTC+1, Dan Vaida wrote:
>
> Greetings everyone!
>
> For a given reason, I need to handle some Route53 records for my EC2's
> EIPs
Greetings everyone!
For a given reason, I need to handle some Route53 records for my EC2's
EIPs.
The instances are part of the [all] group in my hosts file.
Obviously, the 'setup' module is not aware of EIPs. But the ec2_facts
module is.
Right now, I'm trying to wrap my head around this desig
$ cat inv
local ansible_connection=local
$ cat playbook.yml
---
- hosts: local
tasks:
- debug: msg="foo"
when: bar is not defined
- set_fact: bar=hello
- debug: msg="baz {{ bar }}"
when: bar is not defined
$ ansible-playbook -i inv playbook.yml
PLAY [local]
ansible cannot find the local win_ping module, it seems an issue with your
ansible installation at your master.
On Tue, Nov 11, 2014 at 4:54 AM, youmarva wrote:
> Hi,
>
> I recently installed Ansible 1.8 on debian 7, I had a problem when testing
> connection
> to a windows machine.
> Here is th
Agree with Ananda ... precisely what I did.
I noticed I was running out of EIPs, each call created a new one but didn't
associate it (as the instance already had one!) ... so I just added a
"when" the instance.public_ip == none ... works like a charm
e
On Friday, 31 October 2014 04:24:15 UTC,
Hello,
I'm having problems with SSH connections hanging seemingly indefinitely. I
don't recognize any patterns as to what tasks or handlers this happens on.
I'm running ansible 1.7.1 on OS X Yosemite against a bunch of ec2
instances. I also deploy to vagrant but don't think it has had similar S
Thanks Brian,
I wanted a confirmation for this because I feel like it makes the roles and
handlers hardly unusable in a real cluster environment
and it shouldn't be addressed with workarounds. I'll try to see if I can
come up with a patch and submit it for review.
On Monday, November 3, 2014
I do this:
# first batch in parallel
6 - hosts:
just a heads up,
I run RH6.5, not able to upgrade at the moment to 6.6 (and it looks like it
wouldn't help either), I have worked around the ControlPersist issue by
installing a openssh6 client on my control host box (/opt/openssh6),
I then have a wrapper script that calls ansible-playbook and s
This works on my machine,
- name: wait for server to come back
local_action: shell while true; do echo "Waiting ..." ; ssh -o
ConnectTimeout=5 -o BatchMode=yes {{ inventory_hostname }} pwd ; [ $? -eq
0 ] && break || sleep 5; done
sudo: false
On Monday, November 10, 2014 10:14:50 AM UT
Same issue with 1.7.2,
I have worked around the ControlPersist issue by installing a openssh6
client on my control host, it helps a lot.
The issue I had mentioned earlier is actually due to ansible vault,
with a set of encrypted vault files:
Nov 11 10:46:22 GATHERING FACTS
Hi Matt,
I just wanted to say that it worked perfectly as you said.
The correct format is:
"{{ hostvars[inventory_hostname]['ansible_bond0.11']['ipv4']['address'] }}"
Thank you very much.
J.
--
On Wed, Nov 5, 2014 at 11:12 PM, Matt Martz wrote:
> According to that error, you have not defi
I am unable to use the 1.8 omit default either
env={{item.container.env|default(omit)}}
One or more undefined variables: 'omit' is undefined
When using the dev version should ansible --version still say 1.7.2?
the 'which ansible' command is pointing to my checkout...
On Tuesday, 11 November 20
I would like to pass arguments to the docker module like so:
- container:
name: 'testa'
image: 'testa'
- container:
name: 'testb'
image: 'testb'
- name: Start docker containers
docker:
args: "{{item.container}}"
with_items: run_docker_containers
But i get th
Hi,
I recently installed Ansible 1.8 on debian 7, I had a problem when testing
connection
to a windows machine.
Here is the error:
root@ansible:~# ansible vm-windows -m win_ping -
<192.168.1.108> ESTABLISH WINRM CONNECTION FOR USER: administrateur on PORT
5986 TO 192.168.1.108
<192.168.1.
30 matches
Mail list logo
