[Bug 1640645] Re: free space check doesn't take into account kernel upgrades

[Brian Murray]

Hello Manna, or anyone else affected,

Accepted ubuntu-release-upgrader into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:16.04.20 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: ubuntu-release-upgrader (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1640645

Title:
  free space check doesn't take into account kernel upgrades

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Committed

Bug description:
  [Test Case]
  If you don't have a separate /boot partition you can create a file which will be loopback mounted as boot and then test having a full /boot.
  1) Install xenial hwe backport kernel
  2) dd if=/dev/zero of=fake-boot bs=1024 count=204800
  3) mkfs -t ext3 fake-boot
  4) copy your real /boot somewhere
  5) sudo mount -t ext3 fake-boot /boot
  6) copy the files from your old /boot into the /boot
  7) fill /boot up some more e.g. fallocate -l 50M filler.txt
  8) upgrade from Trusty to Xenial (do-release-upgrader)

  With the version of the release-upgrader in the archive you'll receive
  an error regarding "gzip: stdout: No space left on device...
  mkinitramfs failure cpio 141 gzip 1".

  With the version of the release-upgrader from -proposed you'll receive
  an error notification that there is "Not enough free disk space" and
  the upgrade will not proceed.

  [Regression Potential]
  There is little chance of regression as we are just checking to see if linux-image or linux-image-debug packages are marked for upgrade.

  Could not install 'linux-image-4.4.0-45-generic'

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.17
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Wed Nov  9 20:11:19 2016
  InstallationDate: Installed on 2015-05-24 (535 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_CA.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-11-10 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1640645/+subscriptions