Open gberche-orange opened 8 years ago
Hi,
We have updated to version 18 and the issue is still there. My ruby knowledge are very low. Don't known how to fix this issue and can't make any pull request.
Are there any plans to fix this issue ?
Regards
When a bosh deployment fails because of a failed vm instanciation, bosh then asks to clean up the failed vms by invoking the cpi
delete_vm
method.In the following scenario, the vcloud cpi fails to perform the delete vms, and would leave a leaking vapp:
1- a vm is requested for creation, but its IP is conflicting with an existing running vm in another vapp. The vapp and vm creation succeed, but the start fails. The vapp remains in the partially powered state.
2- the vapp is asked for deletion by the CPI, but vcloud is refusing the delete request because the vm is in the partially started state.
Currently in 0.7.10, the
delete_vm
translates to a straight call to the vcloud api DELETE vapp . It should check the entity state to first power off the vms, prior to send the delete requesthttps://github.com/cloudfoundry/bosh_vcloud_cpi/blob/47b2b0aae14436c511c1935bfc33fd85f620c1a5/lib/cloud/vcloud/steps/delete.rb#L8
See vcloud REST API manual at http://pubs.vmware.com/vcd-55/topic/com.vmware.ICbase/PDF/vcd_55_api_guide.pdf p38
Nb: duplicating https://github.com/cloudfoundry-attic/bosh_vcloud_cpi/issues/15 as the repo was moved to the cloudfoundry-attic and does not seem to get attention anymore