Devices running M48 pointing to https://tools.google.com/service/update2 unable to update. |
|||||
Issue descriptionSeeing an odd trend with users running M40 from Auron Yuna or Auron Paine that may suggest an issue with Auto Updates. Auron Yuna = Acer Chromebook 15 (released in Feb 2015) Auron Paine = Acer C670 Chromebook 11 (released in April 2015) For reports with Chrome OS version, device, and auto update server information available, 45% were from users running M40 on Auron Yuna or Auron Paine (Acer) Chromebooks pointing to https://tools.google.com/service/update2 This seems odd. Some of the users claimed that they just purchased the machine and were unable to update it.
,
Aug 18 2017
,
Aug 29 2017
Another similar report: https://listnr.corp.google.com/product/208/report/71818949968 CHROME VERSION: 48.0.2564.116 CHROMEOS_AUSERVER: https://tools.google.com/service/update2 open_in_new CHROMEOS_RELEASE_BOARD: panther-signed-mpkeys CHROMEOS_RELEASE_DESCRIPTION: 7647.84.0 (Official Build) stable-channel panther CHROMEOS_RELEASE_TRACK: stable-channel CHROMEOS_RELEASE_VERSION: 7647.84.0 ENTERPRISE_ENROLLED: Not managed
,
Aug 29 2017
,
Aug 29 2017
Customers are reporting that they are getting errors that their browser is not supported, but they are not able to update. We've received 104 reports from 79 people in the last 90 days -- all where AU Server - https://tools.google.com/service/update2. Top devices for this issue are: Daisy, Panther, Falco, Gnawty, and Auron_Yuna. Here's a similar report, also from Panther device from a Googler: https://listnr.corp.google.com/product/208/report/71747785172
,
Sep 8 2017
For example, I have 7 reports in August from Panther users on 48.0.2564.116 (non-managed devices) who all happen to be on https://tools.google.com/service/update2. One example is https://listnr.corp.google.com/product/208/report/72000820368
,
Sep 8 2017
Ah, here it is. In August, we have 273 reports for all feedback issues from customers in August where AU Server = https://tools.google.com/service/update2, but none of them are running anything past 48.0.2564.116. (And less than 3% are managed). So, there's a number of devices running very old builds, all of which are pointed to the same AU server.
,
Sep 13 2017
Spoke with the TPMs. These users may need to reboot their computers. It looks like some just need to reboot and others may be on cellular connections (including cellular modems). Update messaging on older builds "no update available" wasn't/isn't super-clear to users that they need to restart for the update to take effect or that updates won't proceed on cellular connections. Will see if there are any relevant forum threads on this to see if we can post there. Or whether instructions on relevant Help Center articles are clear.
,
Jun 4 2018
Adding the conops Chrome OS hotlist. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by trumbull@chromium.org
, Aug 17 2017