AWX job starting before vm customizations finishes

gaprindashvili
providers
#1

Not sure if something changed from vSphere 6.5 to 6.7 but the awx job is kicking off before the vm finishes its customization, so its failing because its getting ip from the template and not the provisioned ip this worked before vcenter upgrade. This is only happening to windows vms, is anyone else having this problem or have a remedy. I’m new to manageIQ so any help would be awesome

#2

we add this wait task to all of our playbooks just in case automate gets ahead


  • name: “Wait 600 seconds, but only start checking after 20 seconds”
    wait_for_connection:
    connect_timeout: 30
    sleep: 20
    timeout: 600
#3

Thanks for the reply, but I don’t think that would work for me. I’m using a catalog bundle that kicks off a awx template, its using manageIQ as dynamic inventory so the job starts with the template ip not the provisioned IP. I ended up creating a inline method that waits until the provisioned IP matches the IP from the service catalog.

Thanks

#4

I have the same issue. Could you share the inline method and where you placed it?

Thanks

#5

I figured it out.

I added a wait_for_ip step
image
image

Here is the wait_for_ip method that looks for the assigned ip from the dialog