Make service liveness checks more consistent / correct
Bug #867674 reported by
Stanislaw Pitucha
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Stanislaw Pitucha |
Bug Description
The scheduler and nova-manage check for service being alive in different ways. Additionally there are issues when the host checking the liveness has clock set N seconds in the future and the checked service just updated the timestamp. Negative time differences (-1 day, +many seconds) were not accounted for properly.
Changed in nova: | |
assignee: | nobody → Stanislaw Pitucha (stanislaw-pitucha) |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → essex-1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-1 → 2012.1 |
To post a comment you must log in.
Note that synchronized clocks is a basic requirement.