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

VM Info for VMs created in error state #102

Open
y2kbadbug opened this issue Jan 31, 2025 · 0 comments
Open

VM Info for VMs created in error state #102

y2kbadbug opened this issue Jan 31, 2025 · 0 comments

Comments

@y2kbadbug
Copy link

So I am learning Golang for a project, and wanted to ask something in comparison to the Python Library ngine-io/cs

So in the Python Library, I can create the VM, and it will return the vm details back right away even if it fails. I noticed that in the Go module, if you do a newVirtualMachineDeployment, if it creates the instance in error state it will return an error, leaving the broken VM in CloudStack.

This makes it impossible to have any automatic cleanup tasks (from what I've tried so far) on VMs that are failed. As we do not have the UUID. I could alter it with listVirtualMachines and provide the name as the keyword, but I do not like this idea in an automated fashion, as it could potentially delete something it shouldn't.

So my questions are

  1. Is this how it was designed to work in CloudStack-Go?
  2. Is there a way to get the vm details when it creates it in error?

I appreciate the support!

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

No branches or pull requests

1 participant