EOL notification system required for HWE kernels in LTSs

Bug #1244438 reported by Andy Whitcroft on 2013-10-24
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
Undecided
Unassigned
landscape (Ubuntu)
Medium
Unassigned
linux (Ubuntu)
Medium
Leann Ogasawara
nagios-plugins (Ubuntu)
Undecided
Unassigned
unattended-upgrades (Ubuntu)
Undecided
Unassigned
update-manager (Ubuntu)
Undecided
Unassigned
update-motd (Ubuntu)
Medium
Ubuntu Security Team

Bug Description

We need to have some mechanism to allow us to record that you have an EOL kernel installed which will no longer receive updates.

For example for the kernel when a kernel is going EOL the last upload should include an appropriate file:

    /var/lib/update-notifier/kernel-eol

We need to coordinate this with the notifier itself to ensure it is displayed.

Andy Whitcroft (apw) wrote :

Landscape ought to detect that a system has an EOL HWE kernel installed and suggest appropriate remediation.

Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Low
importance: Low → Medium
Changed in update-motd (Ubuntu):
importance: Undecided → Medium
assignee: nobody → Ubuntu Security Team (ubuntu-security)
Changed in linux (Ubuntu):
assignee: nobody → Ubuntu Kernel Team (ubuntu-kernel-team)
Changed in landscape (Ubuntu):
importance: Undecided → Medium
Robie Basak (racb) wrote :

Consider a debconf high priority notice on the final update (postinst?). Or something else that will generate a root email, perhaps?

Marc Deslauriers (mdeslaur) wrote :

A root email isn't enough for desktop users.

I believe at the last sprint we had discussed having update manager inform the user, and to have the kernel available as an update in update-manager but unchecked by default, so the user needs to opt-in to it.

Changed in linux (Ubuntu):
assignee: Ubuntu Kernel Team (ubuntu-kernel-team) → nobody
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
Andy Whitcroft (apw) on 2013-11-28
Changed in linux (Ubuntu):
assignee: Canonical Kernel Team (canonical-kernel-team) → Andy Whitcroft (apw)
Steve Magoun (smagoun) wrote :

Canonical's OEM preinstall team would like to have a way to control the timing of the update. One way to do this is to provide a way to opt-out of the default upgrade notification, such as by dropping a file on disk via a software update delivered only to those OEM preinstall machines (we have a way to do this already). The second part of the request is a way to opt in/trigger the notification to the end user.

The reason is that Canonical in conjunction with OEMs will do upgrade tests on preloaded hardware to ensure that end users with this hardware have a smooth upgrade path to the next LTS kernel. We'd like to delay the upgrade notifications until those upgrades are tested.

Robie Basak (racb) wrote :

It might also be worth considering what users already use to monitor their machines for updates, and to provide alerts by patching those mechanisms. For example, we might SRU a patch to the check_apt nagios plugin to pick up the EOL kernel state and present it as a warning or failure.

What other mechanisms are in use today?

Changed in nagios-plugins (Ubuntu):
status: New → Triaged
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in landscape (Ubuntu):
status: New → Confirmed
Changed in unattended-upgrades (Ubuntu):
status: New → Confirmed
Changed in update-manager (Ubuntu):
status: New → Confirmed
Changed in update-motd (Ubuntu):
status: New → Confirmed

Am 30.01.14 20:31, schrieb Robie Basak:
> It might also be worth considering what users already use to monitor
> their machines for updates, and to provide alerts by patching those
> mechanisms. For example, we might SRU a patch to the check_apt nagios
> plugin to pick up the EOL kernel state and present it as a warning or
> failure.

Depending on such an implementation (for example adding those feature
with a switch) we may include this patch in Debian.

description: updated
Adam Conrad (adconrad) wrote :

So, if all these update notification things check a single semaphore file, say "/var/lib/update-notifier/no-hwe-oel-warning", then the OEM people can drop that flag in place on a forced update, to avoid their users being notified of stack upgrades before they've validated the upgrade path.

Steve Magoun (smagoun) wrote :

Should we include the name of the base OS in the semaphore, e.g. /var/lib/update-notifier/no-12.04-hwe-eol-warning ?

Andy Whitcroft (apw) on 2015-01-21
Changed in linux (Ubuntu):
assignee: Andy Whitcroft (apw) → Leann Ogasawara (leannogasawara)
Changed in landscape (Ubuntu):
status: Confirmed → Won't Fix
Changed in linux (Ubuntu):
status: Triaged → Fix Released
Changed in nagios-plugins (Ubuntu):
status: Triaged → Won't Fix
Changed in unattended-upgrades (Ubuntu):
status: Confirmed → Won't Fix
Changed in update-manager (Ubuntu):
status: Confirmed → Fix Released
Changed in update-motd (Ubuntu):
status: Confirmed → Fix Released
Changed in ubuntu-release-notes:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers