You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have an image that is quite big and it takes some time to deploy it, the connection to the vcenter might drop and then the whole deploy operation will fail, while leaving a vm instance already deployed.
after the ovftool deployed the vm, the code tries to get the folder object, but if the session is already disconnected, you'll get an error from that line.
The error that you'll see will complain about the folder could not be found, while the problem is the session.
At that point there is no rollback and the deployed vm will remain in vcenter, while CS is not aware of it to clean it up later.
The text was updated successfully, but these errors were encountered:
The last one that failed was about 2.5GB (the ovf is small but the vmdk is large).
The file path being used is located in a remote location.
Something like this path: http://vcenter/Release/5/virtual-appliance/abcd.ovf
Also, this is not using the latest version of the vcentershell, but the code looks the same in the area where it fails, so it would be good to validate it.
If it's not failing with 2.5GB try with bigger files.
If you have an image that is quite big and it takes some time to deploy it, the connection to the vcenter might drop and then the whole deploy operation will fail, while leaving a vm instance already deployed.
https://github.com/QualiSystems/vCenterShell/blob/develop/package/cloudshell/cp/vcenter/vm/deploy.py#L178
after the ovftool deployed the vm, the code tries to get the folder object, but if the session is already disconnected, you'll get an error from that line.
The error that you'll see will complain about the folder could not be found, while the problem is the session.
At that point there is no rollback and the deployed vm will remain in vcenter, while CS is not aware of it to clean it up later.
The text was updated successfully, but these errors were encountered: