community.vmware

community.vmware copied to clipboard

SUMMARY

When triggering a reboot of a host, ansible should wait for the host to reboot.

I am unsure if waiting for the reboot is always recommended, particularly as this is a change from what the module does now. Would it be preferred to add a new state reboot-host-wait or ad a new parameter wait to actively select this behavior?

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

vmware_host_powerstate

ADDITIONAL INFORMATION

Build failed.

• ansible-tox-linters : SUCCESS in 5m 33s
• build-ansible-collection : SUCCESS in 6m 06s
• ansible-test-sanity-docker-devel : SUCCESS in 11m 39s (non-voting)
• ansible-test-sanity-docker-milestone : SUCCESS in 9m 35s
• ansible-test-sanity-docker-stable-2.11 : SUCCESS in 11m 27s
• ansible-test-sanity-docker-stable-2.12 : SUCCESS in 10m 01s
• ansible-test-units-community-vmware-python27 : SUCCESS in 6m 44s
• ansible-test-units-community-vmware-python36 : SUCCESS in 7m 07s
• ansible-test-units-community-vmware-python37 : SUCCESS in 7m 15s
• ansible-test-units-community-vmware-python38 : SUCCESS in 5m 42s
• ansible-test-cloud-integration-vcenter7_only-python36-stable211 : SUCCESS in 23m 40s
• ansible-test-cloud-integration-vcenter7_2esxi-python36-stable211 : SUCCESS in 23m 27s
• ansible-test-cloud-integration-vcenter7_1esxi-python36-stable211_1_of_2 : FAILURE in 18m 29s
• ansible-test-cloud-integration-vcenter7_1esxi-python36-stable211_2_of_2 : SUCCESS in 52m 59s
• ansible-galaxy-importer : SUCCESS in 6m 09s