[ansible-project] blank [ERROR]: when running ansible or ansible-playbook on ansible version 2.5.1

Hi, I am using ansible version 2.5.1 on Centos 7. Whenever I try to use ansible command line or ansible-playbook with ec2.py on AWS I get a " [ERROR]:" after Using /etc/ansible/ansible.cfg as config file. The playbook runs fine after showing one blank error word. I tried using but the

Re: [ansible-project] command using pipes does not work when using ansible without a playbook

Hi Kai, Did not know that I had use shell. Thanks . Works OK. ansible -i ./ec2.py 192.168.108.53 -m shell -s -u ansible -a "rpm -qa --last | grep kernel" Regards, Abey On Tuesday, March 27, 2018 at 2:54:19 PM UTC+1, Kai Stian Olstad wrote: > > On Tuesday, 27 March 2018 15

[ansible-project] command using pipes does not work when using ansible without a playbook

Hi, I would like to use ansible to execute commands on a host. This works ansible -i ./ec2.py 192.168.108.53 -s -u ansible -a "rpm -qa --last kernel" This does not work as expected the output of rpm is given as the final output. I would like to filter the output further. ansible -i

[ansible-project] ansible shell module passing backslashes with double quotes

Hi, I am trying to execute the command 'aws --debug waf-regional associate-web-acl --web-acl-id {{ ACLid }} --resource-arn {{ LBARN }}' via module shell or command but I am getting errors. aws command uses the boto and boto is getting requests with backslashes \"WebACLId\" instead of

Re: [ansible-project] new AWS EC2 instance created using ansible does not use SSD

ed. > > On 27 October 2015 at 09:10, Abey Thomas <abe...@gmail.com> wrote: > >> Hi , >> >> I am trying to create EC2 instances using ansible module ec2 and the root >> volume gets created as "standard". I would like that to be "gp2" &g

[ansible-project] new AWS EC2 instance created using ansible does not use SSD

Hi , I am trying to create EC2 instances using ansible module ec2 and the root volume gets created as "standard". I would like that to be "gp2" Below is the play that I am using - name: Launch the new EC2 Instance ec2: group: '{{ security_group }}' instance_type: '{{

[ansible-project] Re: ec2_group does not honour empty 'rules_egress:'

Hi Barry, works for me if purge_rules and purge_rules_egress is true. - name: Declare api-service ELB security group ec2_group: name: {{env_prefix}}api-service-elb description: API Service ELB security group vpc_id: {{ec2_vpc_id}} state: present