cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4379) vm states can become orphaned if hosts are removed
Date Sat, 17 Aug 2013 05:25:47 GMT


ASF subversion and git services commented on CLOUDSTACK-4379:

Commit 8001e270bb157cd50c252fe5a38ec70c84451ad8 in branch refs/heads/4.1 from [~mlsorensen]
[;h=8001e27 ]

CLOUDSTACK-4379: Reset VM states when host is removed from cluster

   If you shut down the agent while VMs are running, the management
server assumes that the VMs are continuing to run. You can then
delete the host while it is in 'disconnected' state, and those VMs
will be unusable, forever in running state. They can't change state
because the host no longer exists. This patch checks for any VMs
that may have been tied to the removed host and resets their state
so that cloudstack can continue to manage them.

> vm states can become orphaned if hosts are removed
> --------------------------------------------------
>                 Key: CLOUDSTACK-4379
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.1
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: Future
> 1. stop guest agent
> 2. stop management server
> 3. start management server
> Host shows as 'disconnected', but VM shows as running. This is fine, as we can only assume
that it is still running... BUT..
> 4. delete host from cloudstack
> Now the VM is orphaned in 'running' state, won't start anywhere, can't stop it.
> I'm trying to come up with a patch that disassociates any VMs from a host when the host
is deleted.

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:

View raw message