As requested in  bug 615002 , I checked for updates and filed a report.

The issue I mentioned was that my Acer R11 was one of those stuck on an older stable version until you all kindly fixed it last June -- but ever since, the R11 does not automatically update (there's never the up-arrow, restart icon).

As such, I periodically visit the about page and click on "check for updates."  If one is available it updates just fine.

My Acer 720 on stable does continue to receive automatic updates.

Thanks

Let's evaluate the feedback reports but looking at AU stats, I do not see an spike in update errors. There are multiple deferred AUs that should apply eventually.

This is a follow up to my previous comment in  bug 615002  on our school R11's failing to update.  

I was unable to duplicate the R11 failure to update today.   They still aren't picking up the update automatically, but at least they are running the manual update fine.

Pre update:
Version 52.0.2743.116 (64 bit)
Platform 8350.68.0 (Official build) stable channel cyan
Firmware Google_Cyan.7287.54.64

Post update (manual):
Version 53.0.2785.129 (64 bit)
Platform 8530.90.0 (Official build) stable channel cyan
ARC Version 3284968
Firmware Google.Cyan.7278.57.82

Above typed, not copy paste, so typos possible.

I understand there was an issue with R11 firmware last spring.   And of course most of our Chromebooks are shutdown all summer.  Is this possibly still the firmware bug?

I couldn't find any feedback reports with description "for abodenha" from any cyan device. All what I found are unrelated.

josafat@, were you able to find those reports?

Found the report by email address: https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:%20oncegruntled@gmail.com&lReport=13141859819

That one's not likely to be useful though since that machine actually IS up to date. :-(

The original report was that people were on 52 or prior and clicking the "check for updates" button and getting the "you're up to date" message.

Yes, for that report, the user is on the stable-channel @ 53.0.2785.144. There are MANY update attempts in the logs, but they all seem to end normally that an update wasn't found.

[1011/102058:INFO:omaha_response_handler_action.cc(56)] There are no updates. Aborting.
[1011/102058:INFO:action_processor.cc(116)] ActionProcessor: finished OmahaResponseHandlerAction with code ErrorCo<IPv6: 23>kError
[1011/102058:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
[1011/102058:INFO:update_attempter.cc(909)] Processing Done.
[1011/102058:INFO:update_attempter.cc(983)] No update.

We do seem to have pushed 53.0.2785.154, I'm not sure why the user isn't getting it, or supposed to get it at all? +ketakid@

The only error I can see in the logs is:

[1130:1130:1011/091615:ERROR:update_engine_client.cc(331)] GetStatus request failed with error: message_type: MESSAGE_ERROR
destination: :1.11
error_name: org.freedesktop.DBus.Error.ServiceUnknown
sender: org.freedesktop.DBus
signature: s
serial: 52
reply_serial: 53

deymo@ can probably comment on this error.

I don't think there is an issue on that feedback report, there are no new updates currently serving for Acer Chromebook R11, the latest one is 53.0.2785.129. (We did push .144 to some users but it was stopped since missing some validation)

We should be releasing latest update today/tomorrow once above validations are completed 

I just wanted to check in to say that for the first time ever my R11 just automatically updated -- with the up arrow notification now showing.  So, it looks like the latest update referenced above did indeed get pushed out to me today.

So if you did something magical, many thanks. 

By the way, in addition to saying thanks I should've pressed my luck in hopes that soon there'll be some option to get rid of the really annoying -- and never used -- notification bell.  I know some notification users needed a way to access the notification system if no messages were waiting (I get it), but I (and many others) do not wish to use notifications, have them all unchecked, and yet we're stuck with a grayed out bell permanently planted like an appendix next to the clock.  No way to click something in settings, or even an app, to make it go away?

Anyway, sorry for the off topic.  And, again, thanks for the help with the update issue.

Per comments #9 and #10, this issue seems to be already fixed.

Some of our R11's are still not updating correctly from 53 to 54. (Did manual updates on most of them to 53 and was hoping auto update would work).   Manual update button is now saying the Chromebook is up to date.  Sent in feedback report with for abodenha comment as requested.

Version 53.0.2785.154 (64-bit)
Platform 8530.96.0 (Official Build) stable-channel cyan
ARC Version 3322987
Firmware Google_Cyan.7287.57.82

I don't believe the R11 has the 54 update. Seeing all of the R11s I see cannot do so.

Latest update is not rolling out yet for Acer R11  

Ah, is there someplace I can look that up next time?  Or some time period I should wait from when the stable release is announced before I start panicking?  One week? Two weeks?  

Hey, everyone in here, I'd like to share my insight:
I also had an R11 that refused to update.
Here's how I solved it:
Follow the steps given here:
https://support.google.com/chrome/a/answer/6238906?hl=en
That led me to Error-messages in the Log like "Unable to receive HTTP Response".
So I took the Chromebook home and connected it to my private Wifi, it immediately started updating. After that I figured my Firewall was set too restrictive and was denying the update request.
It's very annoying that the Chromebook reports successfully checking in, and then having no update, despite obviously not being able to reach the server at all.

But, yeah, this has solved it for me now :)