Package lists are not updated before Unattended upgrades runs automatically.

[Jarno Suni]

Newest kernel available currently is 4.4.0-31-generic, but

$ linux-version list
4.2.0-38-generic
4.4.0-24-generic
4.4.0-28-generic

`apt-get dist-upgrade` does not upgrade kernel either, unless I run `apt-get update` first.

I wonder why kernel was not upgraded 2016-07-16 morning.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Jul 16 11:40:07 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-21 (237 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: Upgraded to xenial on 2016-06-24 (21 days ago)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "0";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-02-15T22:39:19.560937
mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2016-06-24T18:13:45.181749

[Jarno Suni (jarnos)]

It seems like package lists are not updated even if they should.

[Jarno Suni (jarnos)]

Today unattended-upgrades did install the new kernel, but I think it should have done it before.

[Mathew Hodson (mhodson)]

Since it did upgrade, it seems like the package list just had not been synchronized yet.

[Jarno Suni (jarnos)]

So how to take care that the list will be synchronized before running unattended-upgrade?

[Jarno Suni (jarnos)]

I am not sure which package is responsible for updating the package list so marking as new.

[Brian Murray (brian-murray)]

Did you manually run unattended-upgrade? Its supposed to be run as part of cron which updates the package lists and then calls unattended-upgrade. See /usr/lib/apt/apt.systemd.daily for details.

[Jarno Suni (jarnos)]

No, I let unattended-upgrade run automatically.

[bedfojo (bedfojo)]

Also having this problem.

Software Updater never automatically launches even if I ask for immediate display of available updates.

Unattended-upgrades never installs anything.

After forcing a reload of package info then rebooting the next day, I got errors from unattended-upgrades:
2016-11-29 21:06:13,620 ERROR An error occurred: 'Could not resolve 'ubuntu.mirrors.skynet.be''
2016-11-29 21:06:13,621 ERROR The URI 'http://security.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gstreamer1.0-plugins-good_1.8.3-1ubuntu1.2_amd64.deb' failed to download, aborting

Looks like both Software Updater and unattended-upgrades are launched before my network is up.

[Jarno Suni (jarnos)]

Brian Murray, what is incomplete, except timing the package list updates before unattended-upgrade?

[Launchpad Janitor (janitor)]

[Expired for unattended-upgrades (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Aex Rauch (centaurie)]

We found a workaround sudo systemctl edit apt-daily.timer with following content [Unit]
After=network-online.target
Wants=network-online.target

Today I recive a mail from unattanded-upgrades

[Jarno Suni (jarnos)]

https://github.com/Debian/apt/commit/b4f32b13055287d2ac46a08255db475af195b5f7

[Julian Andres Klode (juliank)]

Fix released, AFAP. There's still some issues on resume only machines that need to be sorted out, but the plan is to deal with that later (it needs a custom online waiting tool to be written).

[Jarno Suni (jarnos)]

I think the fix is not released in Ubuntu, yet. If the target apt release is 1.4.6, which I found in the linked GitHub page, it is not even in Artful, yet.

[Julian Andres Klode (juliank)]

No, it's 1.4.1, as the github page links.

[Jarno Suni (jarnos)]

Still not in the latest release of Ubuntu, which is zesty currently.

[Julian Andres Klode (juliank)]

Released versions do not matter regarding the overall bug state. That bug has been fixed in an update to xenial, yakkety, and zesty; which is in the unapproved queue, but has a slightly annoying regression (and that regression was fixed in 1.4.6). I should update the SRUs now, but associating a new bug with that retroactively (changing a changelog entry from months ago) looks a bit weird.