[Bug 1618900] Re: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

[Timo Aaltonen]

Hello Guillaume, or anyone else affected,

Accepted unattended-upgrades into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.92ubuntu1.2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: unattended-upgrades (Ubuntu Yakkety)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: unattended-upgrades (Ubuntu Xenial)
       Status: In Progress => Fix Committed

-- 
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/1618900

Title:
  [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  There are some race conditions in unattended-upgrades when it is used in shutdown mode. It is possible that the network has already been brought down or for a local file system, like /var/, to be unmounted before the unattended-upgrades script is run.  This then causes the updates not to be installed thereby making systems less secure - if security updates are enabled.

  [Test Case]
  Because this is a race condition, I haven't actually been able to recreate the bug.  However, the fix is straightforward and testing for regressions should be sufficient.

  1) On a freshly installed system.
  2) Modify /etc/apt/apt.conf.d/50unattended-upgrades so that 
  Unattended-Upgrade::InstallOnShutdown "true"; is not commented out.
  3) Reboot and watch updates being installed
  4) Verify updates were installed by reviewing /var/log/unattended-upgrades/unattended-upgrades.log
  5) Uncomment -updates in 50unattended-upgrades

  Repeats steps 3 and 4 again. There isn't any need to run unattended-
  upgrades in *not* shutdown mode because we have only modified the
  systemd service file.

  [Regression Potential]
  There is little chance of a regression, but because of the change (and this feature now working better) its possible the shutdown process will take longer and surprise users.

  Original Description
  --------------------

  Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we encounter the following systemd dependencies issues :
  - The network is often down when unattended-upgrades is running, so packages can not be downloaded (can be mitigated by using APT::Periodic::Download-Upgradeable-Packages "1";) :
      => ERROR An error occurred: 'Could not resolve host: ****.fr'
      => ERROR The URI 'https://****.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb' failed to download, aborting
  - Important mountpoints like /boot are unmounted before unattended-upgrades is running, so newer kernels can not be installed properly (ramdisk and grub configuration can not be generated)

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