Issue
While using this command for automation, there is an inconsistent behavior.
On a few attempts the vapp gets deployed from template successfully and is powered-on as expected but it most cases vapp gets created but does not power-on. Task status shows as "Failed". Still the vapp could be powered on manually from ui.
Quoting a general observation with VCD automation, which might in case cause this issue:
As a general observation there is a latency issue between the actual vapp powerstates visible to org user and the actual power state of the vapp maintained internally. This is causing a lot of automation cases break and forces us to write unconditional waits based on defined vcloud vapp state model.
VCD-CLI command used: vcd vapp create -d vapp-withvcd -c catalog -t test_vapp_mysql -n xyz -i DHCP -m 4096 -u 2 -k 20000 -v vcd-vm-01 -o vcd-vm-1.test.local -a True
Issue While using this command for automation, there is an inconsistent behavior.
On a few attempts the vapp gets deployed from template successfully and is powered-on as expected but it most cases vapp gets created but does not power-on. Task status shows as "Failed". Still the vapp could be powered on manually from ui.
Quoting a general observation with VCD automation, which might in case cause this issue: As a general observation there is a latency issue between the actual vapp powerstates visible to org user and the actual power state of the vapp maintained internally. This is causing a lot of automation cases break and forces us to write unconditional waits based on defined vcloud vapp state model.