Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy from image might fail after deploying the image itself #988

Open
kalsky opened this issue May 19, 2020 · 3 comments
Open

Deploy from image might fail after deploying the image itself #988

kalsky opened this issue May 19, 2020 · 3 comments

Comments

@kalsky
Copy link
Contributor

kalsky commented May 19, 2020

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.

@Costya-Y
Copy link
Contributor

hi,

How big was your image? So we can try to reproduce.

Thanks

@kalsky
Copy link
Contributor Author

kalsky commented May 20, 2020

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.

@Costya-Y
Copy link
Contributor

@turkovda can you please try to replicate this issue in our local center?

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants