© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
5466644
demo site
(Get the code!)
Heartbeats stop working when you mess with the system time. If a monotonic clock were used, they would continue to work when the system time was changed.
Steps to reproduce:
* List the nova services ('nova-manage service list'). Note that the 'State' for each services is a happy face ':-)'.
* Move the time ahead (for example 2 hours in the future), and then list the nova services again. Note that heartbeats continue to work and use the future time (see 'Updated_At').
* Revert back to the actual time, and list the nova services again. Note that all heartbeats stop, and have a 'State' of 'XXX'.
* The heartbeats will start again in 2 hours when the actual time catches up to the future time, or if you restart the services.
Here's example output demonstrating the issue:
http://
See bug #1450438 for more context:
https:/
Long story short: looping call is using the built-in time rather than a monotonic clock for sleeps.
https:/
Oslo Service: version 0.11
Nova: Master (commit 2c3f9c339cae245