[Bug 1723761] Re: unattended-upgrade hangs on shutdown when network is required for updates

[Balint Reczey]

There are two modes of running u-u chosen by setting Unattended-
Upgrade::InstallOnShutdown to "false" (default) or "true".

When InstallOnShutdown is "false" apt's apt-daily-upgrade.service runs
u-u thus this service needs to ensure that network is still up, to not
break similar packages.

Note that while vast majority of packages do not need network connection
during installation a small fraction of them do perform downloads thus
apt's service should try to keep the network up.

When InstallOnShutdown is "true" unattended-upgrades.service is
responsible for keeping the network connection up and I believe versions
starting with 0.93.1+nmu1 are fixed.

** Also affects: apt (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: unattended-upgrades (Ubuntu)
       Status: New => Fix Released

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

Title:
  unattended-upgrade hangs on shutdown when network is required for
  updates

Status in apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Recently an update for flashplugin-installer on xenial was available
  in the ubuntu repositories.

  During the installation of this package a blob is downloaded from
  Adobe servers, which requires network connectivity/internet access.

  Because the network interface(s) have already stopped when this
  package is installed, the server cannot be reached, thus blocking the
  shutdown process until a timeout kills the unattended-upgrades
  process.

  On my machines the shutdown takes about 30 minutes in this case. The
  systemd configuration is standard here, except for a few additional
  services.

  A possible fix could be adding After=network-online.target
  NetworkManager-wait-online.service to After= in the systemd unit file.

  As a workaround I pinned the flashplugin-installer to -1:
  #echo >/etc/apt/preferences.d/forbid_flashplugin "\
  Package: flashplugin-installer
  Pin: release *
  Pin-Priority: -1";

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1723761/+subscriptions