* It is also there is a setting here that I overlooked.
should have been:
It is possible also there is a setting here that I overlooked.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
This may or may not be an issue, but here are my observations. The order
of operations seems to be the cause of my issue with the additional
factor that the /boot partition size is unusually small compared to
recent Ubuntu installations.
Order of operations as follows:
1. unattended-install
Is this still an issue?
I have Xenial installs where this occurs occasionally. I don't have much
information other than /boot partition fills where we will get alerts.
After logging in and running apt-get autoremove the space is cleared.
apt-mark showauto 'linux-image-.*'
Show 3 kernels, which I
However, if I do not run unattended-upgrades with --dry-run before
running without it, automatic removing of unneeded packages works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Mikko Pesari, oh the packages are not actually removed in Wily, either.
I was fooled by the output of the unattended-upgrades command.
costinel, you were right about --dry-run not removing the packages. I
corrected my bug report (bug #1544942).
--
You received this bug notification because you
costinel, In bug #1544942 I run with --dry-run two times and do not
compare outputs between with --dry-run and without it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
As for bug #1544942,
It is reported on Wily, which has newer version of unattended upgrades,
so it may behave differently.
I think command
/usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all
Happens on Trusty and Xenial too. There are a few bug reports about it
marking kernels as manually installed. They may be related. Here's a
test case anyway:
Normal run:
# apt-get install lolcat
# apt-mark showmanual lolcat
lolcat
# apt-mark auto lolcat
lolcat set to automatically installed.
#
I tested on Precise. When running with --dry-run, unattended-upgrade
marks the autoremovable packages as manually installed. This prevents
them from being removed when running without --dry-run afterwards. Check
"apt-mark showmanual".
--
You received this bug notification because you are a
> the --dry-run removes the packages
no, it doesn't. #1544942 affects only one person, and in comment #64 you
can see that files on /boot are not removed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
and #1544942 does not say dry-run removes packages, but says the output
is different between with and without dry-run (which is something I also
observed but only the first run after the upgrade to latest precise
version of unattended-upgrades)
--
You received this bug notification because you
costinel, the --dry-run removes the packages, see Bug #1544942.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
> have you made sure you manually set that option to 'true'?
also, if you pay attention to my pasted logs, THE FIRST TIME the updated
version is run with -d --dry-run, it DOES mention wanting to remove kernels.
however the second time I run it, without --dry-run, it NO LONGER mentions
removing
here is another box
oot@wifi:~# eatmydata apt-get install unattended-upgrades
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
bsd-mailx
The following packages will be upgraded:
unattended-upgrades
1 upgraded, 0 newly installed, 0 to
> have you made sure you manually set that option to 'true'? It's
'false' by default.
yes,
root@mailhost:~# grep Dependencies /etc/apt/apt.conf.d/50unattended-upgrades
Unattended-Upgrade::Remove-Unused-Dependencies "true";
root@mailhost:~# ls -lht /etc/apt/apt.conf.d/50unattended-upgrades
@costinel: have you made sure you manually set that option to 'true'?
It's 'false' by default. For the record, this is what it looks like with
a completely fresh vagrant VM for Ubuntu Precise.
vagrant@vagrant-ubuntu-precise-64:~$ sudo unattended-upgrade --debug
Initial blacklisted packages:
worse, before running unattended-upgrades, apt-get autoremove showed
lots of kernels good for removal. after upgrading and running the new
unattended-upgrades, apt-get autoremove no longer lists these kernels at
fit for autoremove.
--
You received this bug notification because you are a member
this bugs says "Precise Fix Released Medium  Brian Murray Edit"
apt-listchanges -a /var/cache/apt/archives/unattended-
upgrades_0.76ubuntu1.2_all.deb says
" unattended-upgrades (0.76ubuntu1.2) precise-proposed; urgency=medium
* cherry pick fix for unused-dependencies removal. (LP:
Peter Grandi, doesn't unattended-updgrades' automatic removal of new
unused dependencies take into account file "/etc/apt/apt.conf.d
/01autoremove-kernels"? `apt-get autoremove` does. BTW. I think
/etc/kernel/postinst.d/apt-auto-removal should be run during boot to
ensure that
@sean-boran, comment #57:
The fix is available in the trusty-updates repository. See this
changelog: http://changelogs.ubuntu.com/changelogs/pool/main/u
/unattended-upgrades/unattended-upgrades_0.82.1ubuntu2.4/changelog
--
You received this bug notification because you are a member of Ubuntu
Hi,
I regularly have systems with /boot full due, I believe, to this issue and had
an example this morning.
Manually running "apt-get autoremove" deleted kernels+headers for the
last 10 kernels or so. How can that be automated?
Above one refers to version .76ubuntu1.2, and I have
# This will simulate the removal of useless packages linked to old kernels
dpkg --get-selections 'linux-*.*.*-*' | grep $'\t''install' | cut -f1 \
| grep -vF "$(uname -r | cut -d- -f1,2)" \
| grep -vF "$(dpkg --get-selections 'linux-*image*' \
| grep -E '^[^0-9]+'$'\t''install$' | cut -f1 | xargs
This bug was fixed in the package unattended-upgrades - 0.76ubuntu1.2
---
unattended-upgrades (0.76ubuntu1.2) precise-proposed; urgency=medium
* cherry pick fix for unused-dependencies removal. (LP: #1267059)
-- Brian Murray Fri, 11 Dec 2015 10:06:00 -0800
**
Note that this long story started from kernel upgrades, and so far
nobody has made an important point...
When you install a new kernel package, you may want to remove all
previous versions indeed, *except* the one that is currently running.
Because if you remove the package for the currently
I tested the version 0.76ubuntu1.2 on a couple of precise VMs and it
works fine on both of them:
root@:~# apt-get autoremove -s
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-image-3.2.0-64-generic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
Hello Nils, or anyone else affected,
Accepted unattended-upgrades into precise-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.76ubuntu1.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
** Changed in: unattended-upgrades (Ubuntu Precise)
Status: Triaged => In Progress
** Changed in: unattended-upgrades (Ubuntu Precise)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Also affects: unattended-upgrades (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: unattended-upgrades (Ubuntu Precise)
Status: New => Triaged
** Changed in: unattended-upgrades (Ubuntu Precise)
Importance: Undecided => Medium
--
You received this bug
This bug was fixed in the package unattended-upgrades - 0.82.1ubuntu2.4
---
unattended-upgrades (0.82.1ubuntu2.4) trusty-proposed; urgency=medium
* cherry pick fix for unused-dependencies removal (LP: #1267059)
-- Michael Vogt Thu, 03 Dec 2015 17:02:17
Could someone with the permissions to do so *please* "Nominate this for
series" - tagging it as also applying to 12.04? - as per my comment #45.
I would, but appear not to have sufficient permission. (Oddly the
"Nominate this for series" option only shows while I'm logged out).
--
You received
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
unattended-upgrades updated openssl this morning on two machines that I
set to use trusty-proposed, and old kernels were removed properly.
Changing status back and edited tag per comment #46.
** Changed in: unattended-upgrades (Ubuntu Trusty)
Status: Confirmed => Fix Committed
--
You
It's just removed a kernel corrctly, so I've tagged as "confirmed"
** Changed in: unattended-upgrades (Ubuntu Trusty)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I'm sure that it's possible to "tag" this as also applying to Precise
(12.04) - but it's not clear to me how to do that. Could someone do so,
or point me to instructions? Thx
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@Steve Brorens: It's actually the little "Tags" section under the bug
description and right before the comments that needs edited. Remove
'verification-needed' and add 'verification-done', and that should be
it!
If you can, you may want to change "Confirmed" back to "Fix Committed" -
that's for
** Patch added: "debdiff with the fix for trusty"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+attachment/4529110/+files/unattended-upgrades_0.82.1ubuntu2.4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I pushed a fix to trusty-proposed, please double check the git diff was
a bit unclean. As much testing as possible is appreicated (work for me).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Hello Nils, or anyone else affected,
Accepted unattended-upgrades into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.82.1ubuntu2.4 in a few hours, and then in the
-proposed repository.
Please help us by testing this
It does indeed also apply to Precise (12.04 LTS ), I have clients with a
number of these having regular problems with this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Nice to see that a LTS-killing bug is taken seriously (after 2 years).
What about Precise? It is affected and has still 1.5y to live.
(Though one might argue that any affected Precise machine must be either
dead or manually patched by now)
--
You received this bug notification because you are
Short version: backports won't work.
Slightly longer version: It's not in trusty-backports, it's not in
vivid-(updates|backports), it is however in wily.
(Yes, I am aware that it's not an LTS and therefore not ideal, I have the same
situation at work.) Information retrieved on 2015-11-30.
--
Just chipping in to say that it's very frustrating to see this marked
with a status of "Fix released".
Perhaps I'm misunderstanding what that implies, but:
- all my servers running 14.04 LTS don't have the fix yet - and apparently
won't get it unless I take action
- if I'm reading the above
** Also affects: unattended-upgrades (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: unattended-upgrades (Ubuntu Trusty)
Status: New => Triaged
** Changed in: unattended-upgrades (Ubuntu Trusty)
Importance: Undecided => High
--
You received this bug
mvo, is this suitable for an SRU? Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
"Unattended-Upgrade::Remove-Unused-Dependencies" does
Is there any news on this being added as a security update to trusty?
I'm beginning to wonder what "LTS" means if a bug that results in every
installation of Ubuntu sooner or later ceasing to receive security
updates does not get pushed out as part of the security updates.
(As someone else
This is causing us issues left and right. Has the backport come through
yet? We are still seeing servers fill up disks because of this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
For what it's worth; I've worked around this by installing the version
from wily on some trusty machines. So far so good. The machines upgrade
daily and old kernels and their headers are removed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Would like to second that this get backported to Trusty and other
supported versions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
Did you even consider providing the fix via SRU?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
Unattended-Upgrade::Remove-Unused-Dependencies
So, there is a fix released, but it is still not in backports for
trusty... how does that help affected users?
Please backport the fix to all currently supported versions of Ubuntu,
and propose it for SRU. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch
This is fixed, I plan to do a backport for 14.04 and 12.04 via the
trusty-backports, precise-backports mechanism.
** Changed in: unattended-upgrades (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I agree with @Jamiejellicoe this ticket should be rated as Security
issue (250) but we are close that (236)...
Having /boot full can lead to kernel, inird image or grub.conf corruption and
on top of that it's blocking new security updates to be applied.
When /boot is full you cannot even purge
In regard to #20:
I've submitted a pull request that *changes the default behavior* of
`Remove-Unused-Dependencies` to remove *all* orphaned packages, here:
https://github.com/mvo5/unattended-upgrades/pull/6/files (1 week as of
this comment)
I've not received any feedback on this yet, though -
For some reason the unattended upgrades script is very picky about which
packages are to be removed. It tries to auto-remove only those packages
that have been made redundant by the current set of updates. However,
installing a new kernel does not make any previous kernel version
redundant
#20: Thanks for the github link.
#21: You are right, for some reason I thought that autoclean does
autoremove. You are not quite correct though: If you upgrade a package,
the list of dependencies may have changed and dependency may have been
dropped. This will then be no longer required, and
As there has been confusion about this apparently:
Marking the packages for upgrade
line 1194: mark_upgrade()
is not the same as upgrading them. The upgrade only happens after the
changes are commited:
line 392: res = cache.commit(install_progress=iprogress)
The output of is_auto_removable
APT::Periodic::AutocleanInterval is kinda documented in
/etc/cron.daily/apt
# APT::Periodic::AutocleanInterval 0;
# - Do apt-get autoclean every n-days (0=disable)
From what I read from the code, it does just that. According to the man
page autoclean clears out the local repository of
Thanks for the link - I didn't realise the code was based on github. I
don't think changing the default behaviour is the solution though - for
a proper auto-remove there is already a variable
`APT::Periodic::AutocleanInterval` in /etc/apt/apt.conf.d/10periodic
(from the update-notifier-common
I've patched the packages for Precise, Trusty and Debian Wheezy.
Although it's been done in a very ugly and quite sloppy way I can
provide the patches.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
P.s. How is this bug not classed as a security risk? When /boot is full
no more security updates can be installed (when the owner of the machine
is lead to believe they are still being installed)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Each day this bug breaks more Ubuntu servers that do unattended-
upgrades, in particular cloud servers with 100GB rootfs. I alone have
a few dozens affected machines.
And it's not totally trivial for Admin Average to diagnose the inode
shortage, realize it's flooded with linux-headers packages,
This is ridiculous, why has this not been fixed yet?
I manage around 100 VM's and this problem is causing me serious
headaches. I simply haven't got time to go round manually autoremoving
old kernals and it would be foolish not to leave unattended security
updates on.
Just because there are only
@Nathaniel: does http://packaging.ubuntu.com/html/fixing-a-bug.html
help?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
This bug is serious (it causes filesystems to fill up on pretty much every
production server that doesn't have a huge root fs).
It has a reasonable looking patch that fixes the problem.
I don't think there is anything to discuss other than: How do we get the fix
into Ubuntu?
--
You received
I can confirm what Nils Toedtmann says. I discovered this bug precisely
because I encountered situation #1089195. This is a serious issue for
any production servers as you want them to get automatic security
updates, but running out of inodes will simply bring them down. I don't
know why this
Apreche: you say it's a serious issue, and I agree with you. Allegedly,
if I look at the stats at the top of the page, this affects me and 34
other users. Though I'm betting that's just the tip of the iceberg.
Informal discussions reveal that bugs need to have thousands indicating
it affects
Note that situation #1089195 is another possible outcome of this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
This is a pretty big issue, as installing Ubuntu server with the
defaults will always create a boot partition, and enabling automatic
updates (which is desirable from a security standpoint) means that every
few weeks kernel updates start failing because the old kernels haven't
been removed.
I
same problem here. ubuntu 12.04.
is there any fix for this available?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1267059
Title:
Lars Heide, your patch works great for me, I think it should be applied
upstream. But some people may find differential behavior
(now_auto_removable-pkgs_auto_removable) safer. Then the right solution
may be: implementing logic described in #7 (in addition to patch from
#4) with adding new config
Actually I just saw that it is semi fixed in 14.04 in the way that
now_auto_removable-pkgs_auto_removable
now reads
now_auto_removable - pkgs_auto_removable
which is also wrong, as
now_auto_removable = set([pkg.name for pkg in cache
if pkg.is_auto_removable])
I checked and apparently now_auto_removable and pkgs_auto_removable are
always the same, as is_auto_removable only returns different results
_after_ the packages have actually been upgraded. Just marking them does
apparently not change the output of is_auto_removable(). I tried to use
the
This thing seems to be broken in 2 ways (on 12.04 at least):
A) Its checking internally for the wrong variable (
now_auto_removable-pkgs_auto_removable instead of now_auto_removable-pkgs) :
Do this and it will actually tell you the packages that are to be removed.
B) It does not actually
** Patch added: correct variable and issue commit
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+attachment/4206463/+files/unattended-upgrade.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The attachment correct variable and issue commit seems to be a patch.
If it isn't, please remove the patch flag from the attachment, remove
the patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
** Tags added: trusty
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided = Medium
** Changed in: unattended-upgrades (Ubuntu)
Assignee: (unassigned) = Michael Vogt (mvo)
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed = Triaged
--
You received this
77 matches
Mail list logo