Make service liveness checks more consistent / correct

Bug #867674 reported by Stanislaw Pitucha on 2011-10-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
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.

Thierry Carrez (ttx) wrote :

Note that synchronized clocks is a basic requirement.

Changed in nova:
importance: Undecided → Wishlist
status: New → Confirmed
Thierry Carrez (ttx) on 2011-10-21
Changed in nova:
assignee: nobody → Stanislaw Pitucha (stanislaw-pitucha)
status: Confirmed → In Progress

Submitter: Jenkins
Branch: master

 status fixcommitted

commit ad74424768463cd6ad02dd9d6fdf64fc7b3bbafb
Author: David Subiros <email address hidden>
Date: Fri Aug 5 16:35:56 2011 +0100

    Improve the liveness checking for services

    With this modification both nova-manage and scheduler use the flag
    service_down_time and check positive and negative values in a
    correct way.
    Fixes bug: 867674.

    Change-Id: I15c48d80cafa2089cd228c09c61b0a1e513730e8

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2011-11-09
Changed in nova:
milestone: none → essex-1
Thierry Carrez (ttx) on 2011-11-17
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers