Hi again. Thanks .. I got so hung up on using with_dict I didn't consider
taking another tack.
I'm reconsidering the decision to not to use hash_behaviour=merge as that
solves my problem + would also come in handy elsewhere, like combining
default sysctl parameter changes with additional
Hi Matt,
We had a lot of requests for pbrun support from some users and customers,
and Brian had already done a lot of work on it for the 1.9 release before
we had originally changed course and decided to make it a 2.0
feature. However, we decided to make it a stretch goal for 1.9, so users
who
If I check a remote dict item (inside a role/playbook), that may not be
present like:
debug msg=JAVA_HOME= {{ ansible_env.JAVA_HOME }}
Then I get the following exception:
TASK: [java-noinstall | debug msg=JAVA_HOME= {{ ansible_env.JAVA_HOME }}
] ***
fatal: [vm] = One or more undefined
Does my example above help you as far as the templating piece?
Personally I would abstract out the desired state for the route-file status
into it's own dict to smth like this:
route_file_state:
routes-other: present
routes-ext: absent
would prevent that extra attribute from
Even though a task is skipped, the registered variable is still created.
You would want to check something like the following on your test 2 task
instead:
when: not test_1|skipped
On Wed, Mar 11, 2015 at 10:06 AM, Marc Patermann
hans.mo...@ofd-z.niedersachsen.de wrote:
Hi,
should this work:
Would you mind sharing the full body of the task that pertains to this as
well as the template file?
On Tuesday, March 10, 2015 at 12:19:46 PM UTC-4, John McNulty wrote:
So the reason why I tried using union was this github issue (
https://github.com/ansible/ansible/issues/7495 ) which
Yes, I can work with that.
Thanks for your help.
On Wednesday, 11 March 2015 17:15:58 UTC, Jonathan Davila wrote:
Does my example above help you as far as the templating piece?
Personally I would abstract out the desired state for the route-file
status into it's own dict to smth like
Just a small quote regarding K-root (DNS) from the good folk at RIPE [1]:
Configuration management of our K-root server platforms is now
automated almost entirely, using a customised tool set based on
Ansible. This eases the day-to-day operations effort for our
Nice, now ansible is part of the basic structure of the internet ...
insert plumbing allegory here.
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
Thanks for the help!
On Monday, February 23, 2015 at 3:44:51 PM UTC-8, Brian Coca wrote:
you indented with_items too much
On Mon, Feb 23, 2015 at 4:42 PM, Chanaka Samarajeewa cha...@jostle.me
javascript: wrote:
Hello,
Can someone please let me know why I am getting this error
Hello,
I am trying to use with_items: from a file but I am getting the following
error. I can't find any documentation to help me with this. I'm hoping
someone can help me. The error message and my files are as follows:
Error:
TASK: [cloudwatch_alarms | include_vars ec2-alarms.yml]
nevermind i figured my ec2_elb problem was though . the instance_ids need
to be passed in via complex args , since they are an array and the standard
key=value argument method would not work here . To workaround this , I
passed the ids through the jinja2 join filter
instance_id: '{{
Update:
This only works when you have value from instance_ids . Having multiple
id's creates a malformed string i-x,i-
while it should look like i-4f8cf126', 'i-0bb7ca62
How can this be fixed ? Any help would be appreciated
On Wednesday, March 11, 2015 at 11:50:16 AM UTC+5:30,
On 11 March 2015 at 00:08, James Cammarata jcammar...@ansible.com wrote:
$ git checkout v1.9.0-0.1.rc1
$ . hacking/env-setup
After which time you can run ansible and ansible-playbook like normal. If
you're not familiar with the hacking/env-setup script, please refer to the
documentation
BTW, if you don't mind -- for those of you who have tested this, please
comment on the pull requests so Brian knows it works as intended.
https://github.com/ansible/ansible-modules-extras/pull/288
https://github.com/ansible/ansible-modules-extras/pull/282
Thanks,
-M
On Tue, Mar 3, 2015 at
Hi,
Below is the playbook, which work fine and create an ec2 instance inside
the Public subnet inside my VPC and register the result inside the ec2
variable, but the problem is sometime the Associate new EIP to the NAT
Instance work and sometime fail, the reason is that, if the Public
subnet
No, we noticed that too, but decided to go ahead with the release candidate
as we weren't sure if it was simply something that needed to be adjusted in
the test due to the PBRun-related changes.
If it's simply test related, we'll put the fix in the final release or the
next RC so it tests
*Is this a bug or am I misunderstanding how variables are resolved based on
precedence? According to http://docs.ansible.com/playbooks_variables.html, *
* extra vars (-e in the command line) always win
* then comes connection variables defined in inventory (ansible_ssh_user, etc)
* then
18 matches
Mail list logo
