MOTD throws upgrade flag on newer systems

[Niklas]

Hey,

There is an error in MOTD on Ubuntu 17.04 after upgrade from 16.04 -> 16.10 -> 17.04. Which throws updateflag from 12.04. This error shows on startup of every ssh session.

Last login: to. april 27 01:19:42 CEST 2017 from 2a02:ffff:f:fff:AA:BB::be41 on pts/2
Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-20-generic x86_64)

Ubuntu 12.04 LTS end-of-life is April 25, 2017 -- Upgrade your Precise systems!
 $ sudo do-release-upgrade -m server

0 packages can be updated.
0 updates are security updates.

By the look of "etc/default/motd-news" it it is a curl som staticly linked motd https://motd.ubuntu.com which prints this.

Quick fix is setting etc/default/motd-news | ENABLED to 0.

update-motd:
  Installed: 3.6-0ubuntu1
  Candidate: 3.6-0ubuntu1
  Version table:
 *** 3.6-0ubuntu1 500
        500 http://no.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
        500 http://no.archive.ubuntu.com/ubuntu zesty/main i386 Packages
        100 /var/lib/dpkg/status

[Manfred Hampl (m-hampl)]

Just to mention an additional discrepancy:
According to https://lists.ubuntu.com/archives/ubuntu-announce/2017-March/000218.html the EOL date of precise is April 28, 2017, why does https://motd.ubuntu.com tell about April 25?

[Steve Langasek (vorlon)]

I believe this is expected and by design, but I'll let Dustin comment.

[Brian Murray (brian-murray)]

This fixes comment #1.

https://code.launchpad.net/~brian-murray/ubuntu-motd/update-date/+merge/323339

[Casper Alant (caalant)]

I just did a new install of Ubuntu Server 17.04 and also received the MOTD.