Which channel are you on?

I'd assume canary, because we never shipped 2905 or 2908 to dev.

Yes, Canary: 56.0.2905.0 (Official Build) canary (64-bit)

borisv@ - any ideas on how to find out why Canary think's it's up to date?

No clue - there isn't any error message. Can you run the diagnostic tool:

/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics

If this file is not there, you must have a system Keystone. Try this one:
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics

Once you run the tool, please upload the generated .zip file with the logs to this bug.

Logs from 56.0.2889.0 (Official Build) canary (64-bit) (I realized that I was previously actually running the binary on the wrong disk -- I just updated my OS, so had the Canary app on multiple disks.  But, I see the same behavior with this version.)

Deleted: KSDiagnostics-500260592.859161.zip 479 KB

KSDiagnostics-500260592.859161.zip 479 KB Download

It sounds like the ticket still points to location on the other disk. Keystone cannot find it and hence ignores it. We should probably error out in that case, though (filed internal b/32721353). I think the current implementation of the Keystone registration framework detects the presence of the Canary ticket, but does not verify the location (I am still confirming).
/Volumes/Macintosh HD 1/Applications/Google Chrome Canary.app

Nov  7 16:20:12, ksadmin[94928] : KSCheckAction ignored these tickets for products that were not installed: {(
		<KSTicket:0x100602df0
			productID=com.google.Chrome.canary
			version=56.0.2905.0
			xc=<KSPathExistenceChecker:0x1006016d0 path=/Volumes/Macintosh HD 1/Applications/Google Chrome Canary.app>
                        ...
			creationDate=2016-11-01 01:48:05

Yeah, that would make sense, and is my bad for accidentally running the wrong binary as the one where I upgraded to a system ticket!  How would I go about resetting the Keystone state?  And, would you like me to hold off on that, in case you'd like additional debug info first?

It is ok, I've got enough data. To fix the problem on your machine, please follow these steps in terminal:
1. cd /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/
2. sudo ./ksadmin -P com.google.Chrome.canary --delete
3. Restart the canary and go to chrome://chrome
4. Click on "Enable Updates for all users". This will create the new ticket with the proper location.

In the meanwhile, I am adding more errors to the Keystone code, so that we tell the user that something is wrong in that case.

This is now fixed internally. Next release of Keystone will start to generate errors in this case. I will resolve the bug when we ship it.

These will be numeric errors, correct? Will the update page display the error codes, or a user readable string?

The error that I just added is this one:

KSUpdateEngine is attempting to update an uninstalled product. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:3010]

Actually, the full text is below:

Update failed (error: 11)

Error details:
KSUpdateEngine is attempting to update an uninstalled product. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:3010]

 Issue 673907  has been merged into this issue.

 Issue 627745  has been merged into this issue.

See also:  issue 677981  (Canary, M57, opened 1/3/17) with a screenshot of the Mac 'Out of date' icon, attached here for reference

Deleted: MacM57UpdateBug677981-C1QTioGUcAAFCaH.png 356 KB

	MacM57UpdateBug677981-C1QTioGUcAAFCaH.png 356 KB View Download

A similar problem was reported in the help forum 1/11 and has been referred here.  Chrome has been out of date for 2 releases, Icon warns 'out of date' but update check reports 'up to date'

https://productforums.google.com/forum/#!topic/chrome/G8MS7JTkJAs

Thank you, larrylaca818, for providing link to this bug in the forum. The release of the updater that provides an error in Chrome should be out soon.

Boris: Thanks.  I was weeding through the details looking for release tags as you were typing.

I don't see any installer CL history here (662228).  Will these show up here?

All: See ksdiagnostics for the installer version ID. The M56 C#6 .zip file above was for 
  Mac OS: Version 10.12.1 (Build 16B2555)
  Google Software Update Version: 1.2.6.1370

All FYI (If you want to dig around):
See also:  issue 592321  (Mac 42.0.2311.135, should be m49), status 3/14/16 WontFix

Recommends:
To find the exact error with updating, please open the Terminal application, copy/paste the text below as a single line and press enter:
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/ksadmin --verbose --list | grep ErrorDomain

By the way, Keystone (the updater) shipped the the change that I mentioned earlier, so now we should see such errors.

larrylaca818@, I am afraid that this change is in the updater code that is not open sourced yet. 

Hello - I am having a similar issue.  I am using Chrome 54.0.2840.71 (64-bit) on Mac OS 10.10.5 and when I go to "About Google Chrome" it tells me it is up-to-date, but the red up arrow to the right of the address bar says "Chrome is Out of Date."  

I am not sure I can re-open this ticket or if this message will show up, but I would appreciate any help to resolve my problem.

Thanks.

Jef@ - Per Boris's comments here, the problem was the keystone updater, itself updated ~March 2017.

Your version of Chrome, 54..71, is even older (10/20/16) than the keystone update.

You can pull the current Chrome from here manually
https://www.chromium.org/getting-involved/dev-channel

and check that Mac updates are current too (for keystone, etc)

OK, thanks Larry - I will download manually and hopefully all will be solved.

If it helps to trace the origin of this bug … from 2012: 

160274 - outdated stable versions of Google Chrome make false statements that they are up-to-date - chromium - Monorail
<https://bugs.chromium.org/p/chromium/issues/detail?id=160274>