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

When destroying VM, inspect (non-) successful job return #155

Open
bheuvel opened this issue Aug 19, 2016 · 0 comments
Open

When destroying VM, inspect (non-) successful job return #155

bheuvel opened this issue Aug 19, 2016 · 0 comments
Labels

Comments

@bheuvel
Copy link
Contributor

bheuvel commented Aug 19, 2016

Example of a response where the job "finished", but informs of an error.

{\"queryasyncjobresultresponse\"=>{\"accountid\"=>\"129cea07-35dd-47bc-bd89-a8b59e9a6211\", \"userid\"=>\"d08a5318-0f15-4c05-a9b7-6ed6466fbbc3\", \"cmd\"=>\"org.apache.cloudstack.api.command.user.vm.DestroyVMCmd\", \"jobstatus\"=>2, \"jobprocstatus\"=>0, \"jobresultcode\"=>530, \"jobresulttype\"=>\"object\", \"jobresult\"=>{\"errorcode\"=>530, \"errortext\"=>\"Parameter expunge can be passed by Admin only\"}, \"created\"=>\"2016-08-19T12:12:57+0200\", \"jobid\"=>\"3a99bde5-c142-400d-9655-174bed03a773\"}}"

In this specific case the CloudStack version only allowed admin to use expunge, and "therefore" did actually not destroy the VM.

@bheuvel bheuvel added the bug label Aug 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant