Jakub Libosvar a84462f698 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@redhat.com>		2020-09-08 12:09:48 -04:00
..
ovn	ovn: Always use UTC for Hash ring timestamps	2020-09-08 12:09:48 -04:00
__init__.py	Reorganize unit test tree	2015-04-06 23:28:31 +00:00
moved_globals_code1.py	debtcollector for globals	2016-08-30 10:18:19 -04:00
moved_globals_code2.py	debtcollector for globals	2016-08-30 10:18:19 -04:00
moved_globals_target.py	debtcollector for globals	2016-08-30 10:18:19 -04:00
test__deprecate.py	Remove the dependency on the "mock" package	2020-04-28 18:05:37 -04:00
test_cache_utils.py	Remove the dependency on the "mock" package	2020-04-28 18:05:37 -04:00
test_coordination.py	Remove the dependency on the "mock" package	2020-04-28 18:05:37 -04:00
test_ipv6_utils.py	Start using oslo_utils.netutils.is_ipv6_enabled()	2019-10-16 21:44:56 -04:00
test_utils.py	Fix R1720 pylint error in test_utils	2020-08-28 17:23:22 -04:00