You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nitesh Sarda (JIRA)" <ji...@apache.org> on 2017/12/06 10:54:00 UTC
[jira] [Updated] (CLOUDSTACK-10176) VM Start Api Job returns
success for failed Job
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nitesh Sarda updated CLOUDSTACK-10176:
--------------------------------------
Description:
*ISSUE :*
VM start API Job returns success for failed Job
*STEPS TO REPRODUCE :*
# Stop VM instance.
# Mark state of associate router as Stopping from DB
# Execute startVirtualMachine Api from rest client.
# VM will not start but still main job will return the status as SUCCEEDED, whereas sub-job for command VmWorkStart will return status as failed.
was:
*ISSUE : *
VM start API Job returns success for failed Job
*STEPS TO REPRODUCE :*
# Stop VM instance.
# Mark state of associate router as Stopping from DB
# Execute startVirtualMachine Api from rest client.
# VM will not start but still main job will return the status as SUCCEEDED, whereas sub-job for command VmWorkStart will return status as failed.
> VM Start Api Job returns success for failed Job
> -----------------------------------------------
>
> Key: CLOUDSTACK-10176
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10176
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Nitesh Sarda
>
> *ISSUE :*
> VM start API Job returns success for failed Job
> *STEPS TO REPRODUCE :*
> # Stop VM instance.
> # Mark state of associate router as Stopping from DB
> # Execute startVirtualMachine Api from rest client.
> # VM will not start but still main job will return the status as SUCCEEDED, whereas sub-job for command VmWorkStart will return status as failed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)