Kernel Kit
Setting new timezone-utc-offset results in odd read back #176
-
|
When playing with the recently added timezone-utc-offset in ietf-system, I ran into an odd issue when reading back the current-datetime from the system operational datastore. This was even more odd when using timezone-name, because the client presents the remote system time with my local timezone. Can anyone please explain this? Btw, I'm using netopeer2-cli. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
The value is transferred correct (with timezone information) from infix, but netopeer2-cli (libyang) is transforming it to a canonical date, which results in that the time is presented in your local timezone in netopper2-cli. You can see more here: CESNET/libyang#2116 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! I had to ask, was not apparent at all(!) from the YANG model. I've tested now with another (Python) client and I can see the XML has the correct value I set before. |
Beta Was this translation helpful? Give feedback.
The value is transferred correct (with timezone information) from infix, but netopeer2-cli (libyang) is transforming it to a canonical date, which results in that the time is presented in your local timezone in netopper2-cli.
You can see more here: CESNET/libyang#2116