Confd_datetime timezone issue

Core Engine and APIs
1

Hi, I noticed that Confd version 6.4.3 does not handle timezone part of of “struct confd_datetime” correctly.
If i set the .“timezone = 0;” and “.timezone_minutes = 10;” i get:
datetime 2020-03-09T10:35:30-00:10 // this should be 2020-03-09T10:35:30+00:10

and in the case of .“timezone = 0;” and “.timezone_minutes = -10;”
datetime 2020-03-09T10:35:20-00:**

Is this a bug or am I doing something wrong?
BR

2

When you write “I get”, what do you mean, in what context? I do not see any issues receiving timestamps with (non-zero) timezones from ConfD, but I did not try with 6.4.3 - it is a bit dated release.

3

I get it via CLI “show datetime”. This action takes confd_datetime structure (with the mentioned timezone values) and prints it on the terminal.

4

I see similarly incorrect behavior with confd-6.5; I could not trace the problem to a changelog note, but it looks like it has been fixed in later releases, can you migrate to a more recent ConfD release?

1 Like
5

See CHANGES in ConfD-6.6.3, ConfD-7.1, ConfD-6.4.8, ConfD-6.5.9, ConfD-6.7.3
“Changed the data type accordingly in order to display timezone=0 in a correct way.”

1 Like