From a8d624c0502c241feadcfba71ba1442b22d9908b Mon Sep 17 00:00:00 2001 From: Satoshi Fujii Date: Fri, 15 Oct 2021 06:55:11 +0000 Subject: Fix microsec timestamp not properly handled Current heartbeat service assumes lastEpochMicrosec timestamp in VES notification is represented as milli-seconds, but some devices sends micro-sec timestamp in the field. In that case, the heartbeat notification was not working due to timestamp comparison was not done properly. Signed-off-by: Satoshi Fujii Issue-ID: DCAEGEN2-2940 Change-Id: Id7c9241de70cb3ff7ee59cf1e2c60089ff96a42b --- Changelog.md | 1 + 1 file changed, 1 insertion(+) (limited to 'Changelog.md') diff --git a/Changelog.md b/Changelog.md index a737ec8..faa6057 100644 --- a/Changelog.md +++ b/Changelog.md @@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/). - [DCAEGEN2-2939] Removed unused code (config\_notif.py) ### Fixed - [DCAEGEN2-2832] Pod become unready state +- [DCAEGEN2-2940] Microsec timestamp not properly handled - [DCAEGEN2-2944] cbs polling process startup failure -- cgit 1.2.3-korg