I have an old playbook that will add an addition volume and it works fine on t2
instances. With the move to t3 instances we also now have nvme based ebs.
The play book uses lvm to setup the second volume we add the volume as xvdf so
/dev/xvdf.
Now on t3 instances when we add the volume as xvdf
look at logs on playbooks that worked are now failing
working task before upgrade
TASK [config-seeding : Clean build directory]
**
Using module file
/usr/lib/python2.7/site-packages/ansible/modules/files/file.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: awx
Work task before upgrade:
TASK [config-seeding : Clean build directory]
**
Using module file
/usr/lib/python2.7/site-packages/ansible/modules/files/file.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: awx
<127.0.0.1> EXEC /bin/sh -c 'echo ~ && sleep 0'
<127.0.
the following play work on t2 instances, the issue I am running into is
when I try to run it against a t3 instance it fails.
it looks like the issue comes from the new instance types are using
/dev/nvme0n1p1 for root and /nvme1n1 for the second drive. t2 vs (t3. m5
,c5)
so is there a ec2 fact th
I am looking for a role or play book that one could run against AWS EC2
instances and set a cloud watch alarm for "cpucreditbalance".
frank
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving em
gt;
> Also, you have provided two different search strings - which one is being
> used by your code?
>
> Regards, K.
>
>
> On Fri, Dec 7, 2018 at 11:37 AM Frank Dias > wrote:
>
>> here are the extra vars being set;
>> account: prod
>> ami_search_string: amz
here are the extra vars being set;
account: prod
ami_search_string: amzn-ami-2018.03.i-amazon-ecs-optimized
asg_name: MiscServices
cluster_name: MiscServices
instance_type: m5.2xlarge
lc_name: MiscServices
region: us-west-2
On Thursday, December 6, 2018 at 2:45:21 PM UTC-6, Frank Dias wrote
uot;failed": true, "msg": "the field 'args'
has an invalid value, which appears to include a variable that is
undefined. The error was: list object has no element 0\n\nThe error appears
to have been in
'/var/lib/awx/projects/_1067__production_us/roles/aw
ami_search_string: "amzn*amazon-ecs-optimized*"
ec2_ami_find:
name: "{{ ami_search_string }}"
region: "{{ region }}"
virtualization_type: hvm
owner: aws-marketplace
sort: creationDate
sort_order: descending
sort_end: 1
register: os_image
when:
- lc_ami is not
I an trying to get set_fact: resource_{{ item.item.key }}={{item.stdout}}
to be the output of "stdout": "0" meaning resource_{{ item.item.key }}=
0, later in other task I am checking if value is 0 or 1
On Wednesday, September 27, 2017 at 9:36:42 PM UTC-5, Frank Dias wrote
Can I get your help in diagnosing why this is not working, I am getting the
error on task #3 Here are the three tasks; I am wantng to key off of
"stdout":
"0",
- name: Check if Redis Resources already exists
shell: "pcs resource | grep '{{ item.key }}' | grep Master | wc -l"
role between OS version.
currently our env is centos6 and plans are not set for when to go to
centos7 as of yet
On Saturday, August 26, 2017 at 9:50:42 PM UTC-5, Frank Dias wrote:
>
> why does this not work?
>
> this is my play;
> - name: install PG HA
> hosts: dbs6
&g
why does this not work?
this is my play;
- name: install PG HA
hosts: dbs6
gather_facts: True
any_errors_fatal: True
vars:
postgres_ha_cluster_master_host: dbs03.prodea-int.net
postgres_ha_cluster_vip: 172.24.2.241
postgres_ha_pg_repl_pass: Pr0d3
13 matches
Mail list logo
