Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6FD6E17BDA for ; Thu, 24 Sep 2015 11:33:24 +0000 (UTC) Received: (qmail 85334 invoked by uid 500); 24 Sep 2015 11:33:24 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 85279 invoked by uid 500); 24 Sep 2015 11:33:24 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 85268 invoked by uid 99); 24 Sep 2015 11:33:23 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Sep 2015 11:33:23 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 715D1E10A4; Thu, 24 Sep 2015 11:33:23 +0000 (UTC) From: anshul1886 To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-8848: extra state to handle; n... Content-Type: text/plain Message-Id: <20150924113323.715D1E10A4@git1-us-west.apache.org> Date: Thu, 24 Sep 2015 11:33:23 +0000 (UTC) Github user anshul1886 commented on the pull request: https://github.com/apache/cloudstack/pull/829#issuecomment-142903425 This simply means that there power_state has not changed for that period of time. As I pointed out in my previous comment that if state is consecutively updated with same power state thrice then we don't update state. If its state gets changed then only we update it. So I am assuming for these routers power_state_update_count is 3. --- 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. ---