once a timezone is set the date command works, however timedatectl does not and the daemon does reset the TZ to nothing
~$ timedatectl
Local time: Mon 2017-03-20 17:39:23 UTC
Universal time: Mon 2017-03-20 17:39:23 UTC
RTC time: Thu 1970-01-01 00:48:33
Time zone: n/a (UTC, +0000)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
pat-mcgowan@localhost:~$ date
Mon Mar 20 13:39:57 EDT 2017
The snapweb UI reflects what timedatectl sees i.e. the wrong timezone.
So this bug seems to be "fixed", will open another on snapweb not to rely on timedatectl.
I reflashed the dragon board to retest
once a timezone is set the date command works, however timedatectl does not and the daemon does reset the TZ to nothing localhost: ~$ date
~$ timedatectl
Local time: Mon 2017-03-20 17:39:23 UTC
Universal time: Mon 2017-03-20 17:39:23 UTC
RTC time: Thu 1970-01-01 00:48:33
Time zone: n/a (UTC, +0000)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
pat-mcgowan@
Mon Mar 20 13:39:57 EDT 2017
The snapweb UI reflects what timedatectl sees i.e. the wrong timezone.
So this bug seems to be "fixed", will open another on snapweb not to rely on timedatectl.