Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 22 Dec 2014 05:21:13 +0000 (UTC)
From: "Koushik Das (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12763166.1419225634000.82415.1419225673640@Atlassian.JIRA>
In-Reply-To: <JIRA.12763166.1419225634000@Atlassian.JIRA>
References: <JIRA.12763166.1419225634000@Atlassian.JIRA>
 <JIRA.12763166.1419225634255@arcas>
Subject: [jira] [Created] (CLOUDSTACK-8103) Vmsync marks VM as stopped even
 after failing to stop it in HV
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Koushik Das created CLOUDSTACK-8103:
---------------------------------------

             Summary: Vmsync marks VM as stopped even after failing to stop it in HV
                 Key: CLOUDSTACK-8103
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8103
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.5.0
            Reporter: Koushik Das
            Assignee: Koushik Das
            Priority: Critical
             Fix For: 4.5.0


Vmsync reports poweroff/powermissing and tries to stop vm. The stop agent command fails as it finds VM to be running in HV. Even though stop command fails, the VM is marked as stopped in the database.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)