It worked with inventory_hostname, however after reboot the playbook execution ends with PLAY RECAP (ok=8, changed=2...).
What can I do to make it execute the rest of the tasks? If I remove the task to reboot, it all goes well. W dniu piątek, 28 marca 2014 16:53:42 UTC+1 użytkownik Brian Green napisał: > > What entry is in your inventory host file? Is it IP address, short > hostname, fqdn? > > The following variables are valid in your playbook, and the 'right' one > depends on your environment. > ansible_fqdn, ansible_hostname, inventory_hostname, > inventory_hostname_short > > The ansible_fqdn and ansible_hostname are facts determined at the remote > host. Inventory_hostname and inventory_hostname_short are parsed from your > Ansible inventory file. > For instance, in your current playbook, if you have an entry for the > reboot target of dbserver, and for some reason the 'dbserver' node reports > its fqdn as webserver.example.org then your reboot command will wait for > webserver.example.org:22 to be available, which may not resolve from your > Ansible management node. > > Given that Ansible has no problem connecting using the value in your > inventory file, you might start with inventory_hostname which will use the > entry in your inventory file. > > Relevant docs here: http://docs.ansible.com/playbooks_variables.html > > > > On Friday, March 28, 2014 10:28:06 AM UTC-5, Rafał Hajduk wrote: >> >> The server reboots very quickly (10-15 seconds), so timeout is not the >> issue. >> >> However the problem might be the FQDN name. I used it because I found it >> in some Ansible snippet. >> >> Which variable should I place there in order to get current host >> rebooted? (in my case it would be xxx) >> >> My hosts file: >> [xxx] >> xxx >> >> W dniu piątek, 28 marca 2014 16:13:27 UTC+1 użytkownik Brian Green >> napisał: >>> >>> If the server is taking a longer than the default timeout value, >>> increase that value. Default is 300 seconds, might need to increase that. >>> >>> http://docs.ansible.com/wait_for_module.html >>> >>> Or there could be a connectivity issue. Is it listening on port 22? Does >>> FQDN name resolution work? >>> >>> On Friday, March 28, 2014 9:00:28 AM UTC-5, Rafał Hajduk wrote: >>>> >>>> Hello >>>> >>>> I want to reboot my server and continue with other instructions. My >>>> code is: >>>> >>>> - name: reboot >>>> command: reboot >>>> notify: >>>> - wait until rebooted >>>> >>>> - name: wait until rebooted >>>> local_action: wait_for host={{ansible_fqdn}} port=22 state=started >>>> delay=30 >>>> sudo: false >>>> >>>> After execution I get an error: >>>> >>>> >>>> failed: [xxx] => {"elapsed": 300, "failed": true, "item": ""} >>>>> msg: Timeout when waiting for myhostname:22 >>>>> >>>>> FATAL: all hosts have already failed -- aborting >>>>> >>>> >>>> How can I fix it? >>>> >>> -- 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 email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5932ccd2-e54c-4e2e-a795-13ade8c72a7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
