[ansible-project] Re: Ansible AWS EC2 create scripts gives this error:: "Timeout when waiting for 172.31.25.6:22"}

2017-12-17 Thread Ajay Sharma
If i increase the delay, in that condition also, it gives the same error. when i ran the above scripts in ansible-playbook --check debug option. it gave this error fatal: [localhost]: FAILED! => {"msg": "'dict object' has no attribute 'instances'"} to retry, use: --limit @/root/insta

[ansible-project] Re: Ansible AWS EC2 create scripts gives this error:: "Timeout when waiting for 172.31.25.6:22"}

2017-12-17 Thread alanpassel7
What happens if you increase the delay? On Wednesday, December 13, 2017 at 3:56:47 PM UTC+11, Ajay Sharma wrote: > > My Ansible AWS EC2 instance creation script gives this error. > > "Timeout when waiting for 172.31.25.6:22"} > to retry, use: --limit @/root/instance/provision-ec2.retry >

[ansible-project] Creating multiple json files with jinja2 loop

2017-12-17 Thread alanpassel7
Hi, I'm trying to create a batch of json files, that will pull values from an inventory group. Ideally, what I would like to have happen is 10 different files are created (the inventory group has 10 nodes in it), using both the position of the node in the inventory list and the fqdn of the nod

[ansible-project] Re: ANSIBLE_KEEP_REMOTE_FILES location on windows target?

2017-12-17 Thread Jordan Borean
Ansible used the TEMP environment variable to determine the path to the temporary folder, so you can just type in *%TEMP%* in Windows explorer to get there for the current user. When doing this through RDP you might be redirected to a folder called 1, 2, 3, ... but that's just an Explorer thing

Re: [ansible-project] Re: Querying Registry and Using Output

2017-12-17 Thread Jordan Borean
No worries, unfortunately package management in Windows is in a pretty poor state as there is no first class manager like yum or apt. Chocolatey is pretty good and I would recommend using it if possible as it abstracts a lot of the information away to the point where you can just mention the pa

[ansible-project] Re: win_Shell or win_command executing a variable taken from win_reg_stat

2017-12-17 Thread Jordan Borean
While you can use win_shell I find it is better to use win_command when it comes to running executables, this way you don't fall prey to the shell specific escaping, e.g. when using win_shell you usually have to do it like; - win_shell: &"C:\Program Files\someapp\app.exe" compared to - win_com

[ansible-project] I an remote to server and login using root just fine, but ansible task is failing

2017-12-17 Thread gitted
My task throws an error as follows: TASK [mysql : Update MySQL root password for all root accounts] failed: [1.2.3.4] (item=127.0.0.1) => {"changed": false, "item": "127.0.0.1", "msg": "unable to connect to database, check

[ansible-project] awx surveys and nested yaml variables don't appear to work as expected

2017-12-17 Thread Brandon Jozsa
Hey everyone. I have some questions about how AWX handles nested yaml values for things like surveys. I have a nested yaml declaration in previous playbook for group_vars, and they look like this: # OS API User Login Information: auth: os_auth_url: "http://openstack.domain.io5:5000"; os_use

[ansible-project] Re: win_Shell or win_command executing a variable taken from win_reg_stat

2017-12-17 Thread 'J Hawkesworth' via Ansible Project
You can pass win_shell a chdir in the 'args' section as well if that helps (may not if a full path is needed). Feel free to go back to your vendor and ask them how their automated testing works if its such a pain to install/uninstall their product. The only way we will get better quality instal

[ansible-project] Re: How to hot deploy to tomcat with ansible?

2017-12-17 Thread 'J Hawkesworth' via Ansible Project
Sorry I thought I had replied to this one days ago. Yes you are right uri doesn't do that so curl would be the only other option I can think of right now. The way we do releases without down time is to have a minimum of two vms running Tomcat and a load balancer in front of them. To deploy, we