There's another issue I noticed in 16.04 that doesn't happen in 14.04:
Initially, the file /etc/apt/apt.conf.d/50unattended-upgrades is as expected, with everything commented out except the "-security" repository, meaning that only security updates will be applied automatically. *However*, after the first time the `unattended-upgrades` program is run, it overwrites the existing `50unattended-upgrades` file (also indicated in the output logs), and adds an additional, uncommented line, which is: "${distro_id}:${distro_codename}";
This could create unexpected and undesirable behavior for a sysadmin. The documentation should instruct the operator to run the unattended-upgrades program once, and correct that file after it runs the first time.
There's another issue I noticed in 16.04 that doesn't happen in 14.04:
Initially, the file /etc/apt/ apt.conf. d/50unattended- upgrades is as expected, with everything commented out except the "-security" repository, meaning that only security updates will be applied automatically. *However*, after the first time the `unattended- upgrades` program is run, it overwrites the existing `50unattended- upgrades` file (also indicated in the output logs), and adds an additional, uncommented line, which is: "${distro_ id}:${distro_ codename} ";
Therefore after first run, the state is:
Unattended- Upgrade: :Allowed- Origins { id}:${distro_ codename} "; id}:${distro_ codename} -security" ; id}:${distro_ codename} -updates" ; id}:${distro_ codename} -proposed" ; id}:${distro_ codename} -backports" ;
"${distro_
"${distro_
// "${distro_
// "${distro_
// "${distro_
};
This could create unexpected and undesirable behavior for a sysadmin. The documentation should instruct the operator to run the unattended-upgrades program once, and correct that file after it runs the first time.