You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2018/09/17 15:29:32 UTC

[GitHub] resmo opened a new issue #2845: VirtualMachinePowerStateSync: New VR not covered in missing VM report

resmo opened a new issue #2845: VirtualMachinePowerStateSync: New VR not covered in missing VM report
URL: https://github.com/apache/cloudstack/issues/2845
 
 
   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   VirtualMachinePowerStateSyncImpl
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master branch.
   -->
   
   ~~~
   4.11.1
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   N/A
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   N/A
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   If a new VR in starting state is missing, cloudstack does not handle the `PowerReportMissing` correctly. Due the fact that the `power_state_update_time` for new VRs is null, the fallback is to use the current time. However, as a result, the grace period will never expire and the VR will not be recreated.
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   1. Upgrade a VR to new template
   2. Delete the new VR before succeeded
   3. In the logs we see
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   2018-09-17 16:11:56,157 DEBUG [cloud.vm.VirtualMachinePowerStateSyncImpl] (DirectAgentCronJob-188:ctx-000b92c1) Detected missing VM. host: 14, vm id: 1545, power state: PowerReportMissing, last state update: 1537193516155
   2018-09-17 16:12:56,037 DEBUG [cloud.vm.VirtualMachinePowerStateSyncImpl] (DirectAgentCronJob-378:ctx-23044819) Detected missing VM. host: 14, vm id: 1545, power state: PowerReportMissing, last state update: 1537193576035
   2018-09-17 16:13:56,141 DEBUG [cloud.vm.VirtualMachinePowerStateSyncImpl] (DirectAgentCronJob-380:ctx-50e528ab) Detected missing VM. host: 14, vm id: 1545, power state: PowerReportMissing, last state update: 1537193636139
   2018-09-17 16:14:56,013 DEBUG [cloud.vm.VirtualMachinePowerStateSyncImpl] (DirectAgentCronJob-382:ctx-91b21df0) Detected missing VM. host: 14, vm id: 1545, power state: PowerReportMissing, last state update: 1537193696012
   
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   VR gets recreated after grace period expired
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   VR was not recreated 
   ~~~
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services