Can we see if this repro's? 

I checked this originally in M56 but haven't looked at it since.
It could be the omaha config for mario no longer has the _eol status entry 

I don't see the EOL flag being set for mario. So that's why. I think there should be a manual rule for this, gkihumba@ can say better.

Tested on M57(9083.0.0) with recovery install and no eol notification at chrome://settings/help.

What is the value if you run the following in the terminal?
$update_engine_client --eol_status

I think only eol status=eol will trigger eol notification.

$update_engine_client --eol_status
EOL_STATUS=supported

I suspect the .mos file eol edits were overwritten...perhaps by manual rules added later. Will do another manual rule and discuss with Moises how we can keep track of versions for rollbacks, if possible.

The lack of updates has been fixed with a repush (b/36216012). I'm handing this over to Grace so that she can add the corresponding manual rules for the notification to appear.

is there a test somewhere we can add to make sure this doesn't revert/break again ?  it's not like the M56/mario client code is going to ever change, and it's going to be more important as we EOL more devices (with alex/zgb up next).

Automated support is coming to GoldenEye. It's been done for canary channel already, but others are more troublesome as there's no easy indication on when to set the flag (canary is easy because GoldenEye itself does the pushes automatically).

GoldenEye has proper tests so once it's automated we can rely on it with more confidence. Support will be added this Q2.

Manual rules have been added

Here (cr48.mos):
https://pantheon.corp.google.com/storage/browser/chromeos-releases-public/payloaddb/

This is a bit outside of the scope of this issue, but maybe not. I really wish we would have EOLed alex and zgb in the same release. Similar with other SOC generations. Creating per-board EOL dates (effectively EOLing leaders before followers) makes things a bit more complicated than it should be. IMHO etc.

i'm not sure mario/alex/zgb were really leaders/followers.  more that they were just the only 32-bit x86 boards we still had.

that said, they had release dates months apart, so if we wanted to clamp at 5 years, we wouldn't be able to anyways.  not that i'm against extending EOL dates when possible :).

All three are pinetrail SOC, mario was leader, alex/zgb followers by today's terminology. But they basically share all bugs/fixes. Same for sandybridge (lumpy/stumpy) and newer Intel SOC generations.

Configs are live.
https://omahaconsole.corp.google.com/diff?pid=189&fromcfgid=323&tocfgid=324&pretty

Mike/ David please test with your Marios to see if eol notification pops up now.

it didn't show the first check, but it showed on refresh.  probably not an edge case that most people will run into, and not like we can fix it now for mario :).

i'm seeing it at the chrome://settings about page, and i'm seeing it when i login as my user.  i'm not seeing it at OOBE or guest mode, but i'm guessing those are unrelated, so i'll file new bugs.

Ok. Marking this as fixed.