[ansible-project] Re: AWS instance profile - how to create in Ansible?

On Friday, May 11, 2018 at 9:06:08 PM UTC-4, Karl Auer wrote: > > I can't figure out how to create an instance profile. > > It's easy enough to attach an instance profile; the ec2_lc module has an > instance_profile_name parameter. > > But how to create the policy and role? > > There seem to be

[ansible-project] AWS instance profile - how to create in Ansible?

I can't figure out how to create an instance profile. It's easy enough to attach an instance profile; the ec2_lc module has an instance_profile_name parameter. But how to create the policy and role? There seem to be three relevant modules, iam, iam_policy and iam_role. iam_role even has a

[ansible-project] Re: backing up a cisco device using telnet

maybe you can try ntc-ansible. https://github.com/networktocode/ntc-ansible On Thursday, February 22, 2018 at 6:08:11 AM UTC-8, Daley Okuwa wrote: > > Is there any information that allows me to backup a cisco device using > telnet rather than ssh as the device do not support SSH > > -- You

Re: [ansible-project] Re: terminating instances

Shit. Ok I'm not home now, but I'll try asap. And resend the email unformatted. Thanks for replying, i appreciate it! On Sat, May 12, 2018, 00:38 Tony Chia wrote: > It seems the "when" for the ec2 task is not lined up. "when" should be > indented at the same level as ec2

[ansible-project] Re: terminating instances

It seems the "when" for the ec2 task is not lined up. "when" should be indented at the same level as ec2 task similar to the debug task On Thursday, May 10, 2018 at 2:27:06 PM UTC-7, David Villasmil wrote: > > hello all, > > I run "ec2_instance_facts" to get some instance_ids: > > -

[ansible-project] Re: Unable to Launch Job Template in Ansible Tower

It appears the search button is search for a key not a job since the "key" button is next to the magnifying glass. Also on the top you have the Azure credential selected. What are you trying to do? Are you trying to search a particular job you created before? Are you trying to search a

Re: [ansible-project] Re: issue with ansible dry-run mode (--check) on package installation tasks (yum and apt modules)

Ok guys, I got the point "--check doesn't make any changes to the system" after making more tests with tasks coupling (Task2 relies on previous executed Task1), --check mode will never work for these cases. Therefore, i will change my test pipeline to discard dry-run mode which has been thought

Re: [ansible-project] Re: terminating instances

On 11.05.2018 19:51, David Villasmil wrote: Anyone able to help? Probably, but as you can see below your mail screwed up any formatting... On Thursday, May 10, 2018 at 11:27:06 PM UTC+2, David Villasmil wrote: hello all, I run "ec2_instance_facts" to get some instance_ids: -

[ansible-project] Re: terminating instances

Anyone able to help? On Thursday, May 10, 2018 at 11:27:06 PM UTC+2, David Villasmil wrote: > > hello all, > > I run "ec2_instance_facts" to get some instance_ids: > > - ec2_instance_facts: > region: us-east-1 > filters: > "tag:Name": "*{{ cluster }}*" > register: ec2_res > > > Then i can

Re: [ansible-project] Unable to use 'yum install'

Hi all, The problem was that the workers needed to be updated with ''yum -y update''. I added the following code to my playbook: - name: yum update yum: name: '*' state: latest Unfortunately I don't know why this solved the problem :( Thanks for helping!

Re: [ansible-project] Unable to use 'yum install'

Hi, Please provide logs to see the exact problem Perhaps information given by a manual yum could help also... But looking for your problem I found some related information that could (not sure) let us know that the problem is somewhere else :

Re: [ansible-project] Unable to use 'yum install'

Hi Jean/js.a I splitted up but the error persists. I'm not sure if my playbook is correct though. Here's the splitted playbook. --- - hosts: all become: yes tasks: - name: install docker yum: name: docker state: present update_cache: true

Re: [ansible-project] question about loop/with_items

On 11.05.2018 10:39, Edmund Cheng wrote: thanks.. do you know why if its 1 server at a time(serial: 1), the play will behave this way? The documentation explains this pretty well https://docs.ansible.com/ansible/latest/user_guide/playbooks_delegation.html -- Kai Stian Olstad -- You received

Re: [ansible-project] question about loop/with_items

Hey Kai, thanks.. do you know why if its 1 server at a time(serial: 1), the play will behave this way? On Friday, May 11, 2018 at 4:11:21 PM UTC+8, Kai Stian Olstad wrote: > > On 11.05.2018 09:33, Edmund Cheng wrote: > > say i have in hosts file 2 nodes. > > > > [nodes] > > server1 > >

[ansible-project] bigip_configsync_action module in Ansible version 2.5 is not working

*bigip_configsync_action module is not working in Ansible 2.5* *ISSUE TYPE* Since from 2.5 version, Ansible added provider to bigip_configsync_action, there is some confusion. bigip_configsync_action module not doing the config-SYNC and keep showing Error as ["Unable to connect to

Re: [ansible-project] question about loop/with_items

On 11.05.2018 09:33, Edmund Cheng wrote: say i have in hosts file 2 nodes. [nodes] server1 server2 in a playbook, we do some loop for tasks. - hosts: nodes with_items : ['apple','banana'] ansible will run it like in the below order: server1 : apple server2: apple server1: banana

Re: [ansible-project] Re: Unable to Launch Job Template in Ansible Tower

On 10.05.2018 22:33, Carlton Patterson wrote: Anybody willing to help out here? This is the list for Ansible Core not Tower, you need to contact RedHat support. -- Kai Stian Olstad -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To

[ansible-project] question about loop/with_items

hi, say i have in hosts file 2 nodes. [nodes] server1 server2 in a playbook, we do some loop for tasks. - hosts: nodes with_items : ['apple','banana'] ansible will run it like in the below order: server1 : apple server2: apple server1: banana server2: banana what if i want to run in