group.of.nepali.translators team mailing list archive

[Mathew Hodson <1906364@xxxxxxxxxxxxxxxxxx>]

** No longer affects: unattended-upgrades (Ubuntu)

** No longer affects: unattended-upgrades (Ubuntu Xenial)

** No longer affects: unattended-upgrades (Ubuntu Bionic)

** No longer affects: unattended-upgrades (Ubuntu Focal)

** No longer affects: unattended-upgrades (Ubuntu Groovy)

** No longer affects: unattended-upgrades (Ubuntu Hirsute)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1906364

Title:
  [SRU] unattended-upgrade still restarts blacklisted daemons

Status in docker.io package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  Fix Committed
Status in docker.io source package in Bionic:
  Fix Committed
Status in docker.io source package in Focal:
  Fix Committed
Status in docker.io source package in Groovy:
  Fix Committed
Status in docker.io source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Docker uses containerd under the hood.  When containerd is upgraded it
  stops and restarts its service; docker stops when containerd stops but
  doesn’t restart.  Particularly when doing unattended upgrades, an SRU
  fix rolled out for containerd can result in unexpected and widespread
  service outages for docker.

  [Test Case]

  $ sudo apt install docker.io
  $ sudo systemctl start docker
  $ systemctl status docker | grep Active
       Active: active (running) since[...]
  $ systemctl status containerd | grep Active
       Active: active (running) since[...]

  $ docker pull ubuntu/redis:latest
  $ docker run -e REDIS_PASSWORD=1234 --network host \
  --name test-redis -d ubuntu/redis:latest
  $ telnet localhost 6379
  $ docker container logs test-redis

  $ sudo apt install --reinstall containerd
  $ systemctl status containerd | grep Active
       Active: active (running) since
  $ systemctl status docker | grep Active
       Active: inactive (dead) since [...]; 8s ago
  $ docker container logs test-redis

  [Where Problems Could Occur]

  The challenge with this issue is addressing all important corner
  cases, and as such the biggest risk is that we miss a corner case and
  fail to keep the two services running when they should.  Areas to
  watch will be failures during start/stop/restart/upgrade type
  operations.  Issues during runtime are unlikely to relate to this
  change.

  [Original Report]

  Hello,

  Today plenty of our systems running ubuntu 20.04 were restarting the
  docker daemon, even if i blacklisted the docker package. Since docker
  has an dependency on containerd thats the reason why it was restarted.
  IMO the blacklist should also check the full tree of dependencies...
  This should NOT happen!

  From the log you find:

  2020-12-01 06:40:13,881 INFO Starting unattended upgrades script
  2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:13,882 INFO Initial whitelist (not strict):
  2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils
  2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2020-12-01 06:40:46,996 INFO All upgrades installed
  2020-12-01 06:40:50,732 INFO Starting unattended upgrades script
  2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:50,733 INFO Initial whitelist (not strict):

  Also this happened for us on plenty of our servers almost at the same
  (why the unattended updates are not spread over time?), which
  destroyed the second time an production environment.

  This is not how unattended-upgraded should be, sadly this package lost
  our trust and we disable it and schedule the 'unattended updates' now
  on our own.

  PS: Not to say that on some servers the docker daemon did not even
  restart..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions