Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: DaanHoogland <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-1997-cloudstack@git.apache.org>
In-Reply-To: <git-pr-1997-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack issue #1997: CLOUDSTACK-9208: Assertion Error in VM_POWER_STATE h...
Content-Type: text/plain
Message-Id: <20170404160841.C5CD5DFCB3@git1-us-west.apache.org>
Date: Tue,  4 Apr 2017 16:08:41 +0000 (UTC)
archived-at: Tue, 04 Apr 2017 16:08:44 -0000

Github user DaanHoogland commented on the issue:

    https://github.com/apache/cloudstack/pull/1997
  
    @jayapalu your check is ok, what is not ok is that it is needed. Somehow a stop can be send to a VM for which no host is known?
    I am worried about the reason of your fix and that we might obscure it. Why is a stop command attempted on a vm for which no host is known?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---