[SRU] Update to containerd 1.3.1

Bug #1854841 reported by George Kraft on 2019-12-02
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
containerd (Ubuntu)
High
Unassigned
Bionic
High
Unassigned
Disco
High
Unassigned
Eoan
High
Unassigned

Bug Description

[Impact]
Docker.io is a fast moving project, and SRU policy for containerd is that getting its .1 update out to LTS users quickly will bring more benefit than risks. This policy was approved by the tech board as of 2016-09-20.

[Test Case]
Checking autopkgtest is sufficient. See https://wiki.ubuntu.com/DockerUpdates for rationale

[Regression Potential]
See https://wiki.ubuntu.com/DockerUpdates for rationale.

[Fix]
1.3.1 is currently in focal-proposed. Any block-proposed tag should be removed to enable it to pass and land, then once migrated can be uploaded for SRU to requested series.

[Original Report]
Hey folks, we've got a Charmed Kubernetes bug[1] that requires us to run containerd 1.3.0+ to fix. Can we get the apt package in bionic universe updated to 1.3.1 or at least 1.3.0?

If possible, we would like to test the updated containerd package in bionic-proposed before it is released.

[1]: https://bugs.launchpad.net/charm-containerd/+bug/1853653

Andreas Hasenack (ahasenack) wrote :

Hello,

can you elaborate a bit more on what bug the update to 1.3.0 is fixing? It's usually better to cherry pick the exact fix needed instead of doing a somewhat big upgrade like this. Also, the 1.3.x series isn't even in ubuntu focal yet (1.3.1 is in focal-proposed).

George Kraft (cynerva) wrote :

We need support for TLS auth with image registries that was added in 1.3.0: https://github.com/containerd/cri/issues/1143

Michael Hudson-Doyle (mwhudson) wrote :

We've been backporting major revisions of docker.io/containerd/runc for the last few years. I think I would still argue this is more useful to end users than targeted cherry-picks.

Bryce Harrington (bryce) wrote :

Indeed, containerd appears to have an SRU special exception granted by tech board:

https://wiki.ubuntu.com/StableReleaseUpdates#Docker.io_group

"""
Docker.io group

The source packages docker.io, containerd, and runc may be uploaded according to the procedure documented in DockerUpdates. Per Technical Board discussion regarding delegation of these decisions to the SRU team, this stable release exception has been approved by BrianMurray for the SRU team as of 2016-09-20.
"""

The approved update policy that applies for this case is:

https://wiki.ubuntu.com/DockerUpdates

From this, Andreas is correct that 1.3.1 needs to be landed in devel first (perhaps it needs the block-proposed tag removed?) and complete migration, before 1.3.1 is uploaded for SRU to bionic.

Changed in containerd (Ubuntu):
status: New → Triaged
Changed in containerd (Ubuntu Bionic):
status: New → Triaged
Changed in containerd (Ubuntu Disco):
status: New → Triaged
Changed in containerd (Ubuntu Eoan):
status: New → Triaged
Changed in containerd (Ubuntu):
importance: Undecided → High
Changed in containerd (Ubuntu Bionic):
importance: Undecided → High
Changed in containerd (Ubuntu Disco):
importance: Undecided → High
Changed in containerd (Ubuntu Eoan):
importance: Undecided → High
tags: added: server-next
summary: - Update to containerd 1.3.1
+ [SRU] Update to containerd 1.3.1
Bryce Harrington (bryce) on 2019-12-04
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.