Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 16 Aug 2013 22:21:47 +0000 (UTC)
From: "Marcus Sorensen (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12664157.1376691597910.83019.1376691707666@arcas>
In-Reply-To: <JIRA.12664157.1376691597910@arcas>
References: <JIRA.12664157.1376691597910@arcas>
Subject: [jira] [Created] (CLOUDSTACK-4379) vm states can become orphaned if
 hosts are removed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Marcus Sorensen created CLOUDSTACK-4379:
-------------------------------------------

             Summary: vm states can become orphaned if hosts are removed
                 Key: CLOUDSTACK-4379
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4379
             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: http://www.atlassian.com/software/jira