[Bug 1687129] Re: Needs to allow updates from the ESM archive

Steve Langasek steve.langasek at canonical.com
Fri May 12 00:38:52 UTC 2017


On trusty, with the faked-up test case I see output such as the
following:

Checking: unattended-upgrades ([<Origin component:'main' archive:'trusty' origin:'UbuntuESM' label:'UbuntuESM' site:'esm.ubuntu.com' isTrusted:False>])
[...]
matching 'o'='UbuntuESM' against '<Origin component:'main' archive:'trusty' orig
in:'UbuntuESM' label:'UbuntuESM' site:'esm.ubuntu.com' isTrusted:False>'
matching 'a'='trusty' against '<Origin component:'main' archive:'trusty' origin:'UbuntuESM' label:'UbuntuESM' site:'esm.ubuntu.com' isTrusted:False>'
pkg 'unattended-upgrades' is untrusted
sanity check failed

So while unattended-upgrades still doesn't install the package, that's
because u-u is too clever for my test case.  It is clear that it is
considering this package differently than it does for linux-libc-dev in
-proposed, which reports:

Checking: linux-libc-dev ([<Origin component:'main' archive:'trusty-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>])
matching 'o'='Ubuntu' against '<Origin component:'main' archive:'trusty-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>'
matching 'a'='trusty-security' against '<Origin component:'main' archive:'trusty-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>'
matching 'o'='UbuntuESM' against '<Origin component:'main' archive:'trusty-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>'
matching 'a'='trusty' against '<Origin component:'main' archive:'trusty-proposed' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>'


so I'm considering this verification-done for trusty anyway.

** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to unattended-upgrades in Ubuntu.
https://bugs.launchpad.net/bugs/1687129

Title:
  Needs to allow updates from the ESM archive

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Precise:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Fix Committed
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Committed

Bug description:
  [SRU Justification]
  When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.

  [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43

  Since the ESM archive contains packages updated by the Ubuntu Security
  team, we should ensure the behavior of unattended-upgrades applies the
  same default policy to both.

  [Test case]
  1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates'
  2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
  3. run 'sudo apt-get update'
  4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
  5. run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
  6. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed.
  7. install unattended-upgrades from -proposed.
  8. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
  9. again run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
  10. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package.

  [Regression potential]
  Worst-case scenario is a bug that prevents future security updates from being applied correctly.  This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+subscriptions



More information about the foundations-bugs mailing list