GitHub user resmo opened a pull request:

    https://github.com/apache/cloudstack/pull/885

    CLOUDSTACK-8848: ensure power state is up to date when handling missi…

    …ng VMs in powerReport
    
    There 2 things which has been changed. 
    
    * We look on power_state_update_time instead of update_time. Didn't make 
sense to me to look at the update_time.
    * Due DB update optimisation, powerState will only be updated if < 
MAX_CONSECUTIVE_SAME_STATE_UPDATE_COUNT; so we can not really rely on these 
information if we can not make sure these are up to date.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/resmo/cloudstack fix/CLOUDSTACK-8848

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/885.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #885
    
----
commit d235255a55883745bac99d5640c965a5a4172a81
Author: Rene Moser <rene.mo...@swisstxt.ch>
Date:   2015-09-24T13:59:36Z

    CLOUDSTACK-8848: ensure power state is up to date when handling missing VMs 
in powerReport
    
    There 2 things which has been changed.
    
    * We look on power_state_update_time instead of update_time. Didn't make 
sense to me to look at the update_time.
    * Due DB update optimisation, powerState will only be updated if < 
MAX_CONSECUTIVE_SAME_STATE_UPDATE_COUNT; so we can not really rely on these 
information if we can not make sure these are up to date.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to