yahoo-eng-team team mailing list archive

[OpenStack Infra <1894117@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/750295
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a84462f698f91b10e332e3403ecc9a68c3e6a884
Submitter: Zuul
Branch:    master

commit a84462f698f91b10e332e3403ecc9a68c3e6a884
Author: Jakub Libosvar <libosvar@xxxxxxxxxx>
Date:   Tue Sep 8 04:38:42 2020 -0400

    ovn: Always use UTC for Hash ring timestamps
    
    When a node is created in ovn_hash_ring table, it used to use timestamp
    depending on the system or mysql timezone. This caused troubles for
    machines using western timezones when getting active nodes before the
    first liveness check, becaus the time difference between UTC and local
    time was always in hours and the limit is 30 seconds.
    
    This patch configures OVN Hash Ring model to always use UTC when
    creating a node so the times are always compared to UTC, regardless of
    the used timezone. Note that the created_at and updated_at are not user
    facing columns.
    
    Change-Id: I9172254ce9b1880833128bdcaacacb93821933dd
    Closes-bug: #1894117
    Signed-off-by: Jakub Libosvar <libosvar@xxxxxxxxxx>


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1894117

Title:
  ovn: filtering hash ring nodes is not time zone aware

Status in neutron:
  Fix Released

Bug description:
  Nodes are registered using local machine timezone but then when
  checking alive nodes. After first touch, the update_at gets fixed
  using UTC timezone and then getting nodes work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1894117/+subscriptions