[
https://issues.apache.org/jira/browse/CLOUDSTACK-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634310#comment-13634310
]
ASF subversion and git services commented on CLOUDSTACK-2067:
-------------------------------------------------------------
Commit 26fea7b660f96292f62c857a03fd6e4faaeba220 in branch refs/heads/master
from Marcus Sorensen <[email protected]>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=26fea7b ]
CLOUDSTACK-2067 - ACS4.2 - throw LibvirtException instead of squelching it
so that callers of startVM in LibvirtComputingResource know that a vm failed
to start
Signed-off-by: Marcus Sorensen <[email protected]> 1366224775 -0600
> KVM virtual machines can fail to start but CS thinks they are running
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-2067
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2067
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Marcus Sorensen
> Assignee: Marcus Sorensen
> Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
>
> When starting an instance, the KVM agent will report success regardless of
> whether or not the domain actually started.
> Introduced by cefece71, we stopped throwing the LibvirtException in
> startDomain. The two places that call startDomain rely on try/catch to know
> if the domain started successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
