New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 887167 link

Starred by 3 users
Status: Archived
Owner: ----
Closed: Dec 20
Cc:
vkasatkin@google.com
marchuk@chromium.org
█ jayhlee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

Auto-update will not happen if datetime was in the far future at least once

Project Member Reported by marchuk@chromium.org, Sep 20 
ChromeOS version: any
ChromeOS device model: any 
Case#: 16902890
P1 due to testing impact


I cannot reproduce it by setting wrong date in root's shell, but it's happening to school:

1. Make a device have very wrong timedate (e.g. due to battery failure, or storing for long time not in "shipping" mode, etc). In our case it became 1/12/2154
2. Turn on the device, observe
[0912/110245:INFO:chromeos_policy.cc(314)] Periodic check interval not satisfied, blocking until 1/21/2154 1:07:43 GMT

Even datetime became correct afterwards thanks to tlsdate, auto-updater "remembered" somewhere that it "should" block periodic check till 1/21/2154 and not performing periodic check anymore.

Logfile attached.
debug-logs_20180912-111730 (1).tgz
206 KB Download

Comment 1 by sylcat@google.com, Dec 14 

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Comment 2 by sylcat@google.com, Dec 20

Status: Archived (was: Untriaged)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.
►

Sign in to add a comment