818226 - ensure the timezone and time are set properly on tegras (and other devices)

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect, P3)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

we need to ensure that the foopy, bm-remote (webserver), and tegras are all on the same timezone and theoretically on the exact same time.

I believe the times are correct, but the timezones might be off.

Comment 1

[Chris AtLee [:catlee]]

Callek, now that we're on the new foopies, is this done? Or easily fixed?

Comment 2

[Justin Wood (:Callek)]

Joel,

Can you tell me how we can check (and set if need be) the timezone on a tegra/panda. Also does said setting method persist across reboots? Does it need a reboot to take affect?

I'll handle foopies/bm-remote*

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

this is how we set the timestamp:
https://hg.mozilla.org/build/tools/file/546cfc026c18/sut_tools/installApp.py#l136

The timezone is similar:
telnet <ip> 20701
tzget
tzset GMT-08:00
tzget

This persists across reboots and I would recommend rebooting to ensure the OS is fully updated.  you can get/set/get without rebooting and it will work.

Comment 4

[Justin Wood (:Callek)]

where does this (older than expected) bug fall on priority list, do we have evidence its a problem or are we just not verifying its ok?

Comment 5

[Joel Maher ( :jmaher ) (UTC -8)]

I honestly have no idea, I suspect this is a lower priority and the action item here is more of a sanity check and a means to help prevent/detect problems.