[Bug 1783597] Re: The disk-space-needed estimate doesn't account for the snaps

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.16.7

---------------
ubuntu-release-upgrader (1:19.04.16.7) disco; urgency=medium

  * DistUpgrade/DistUpgradeQuirks.py, DistUpgrade/DistUpgradeCache.py:
    Modify DistUpgradeQuirks to calculate extra space needed for snaps that
    need to be installed during upgrade (replacing old debs) and add that to
    estimates done in checkFreeSpace(). (LP: #1783597)
  * DistUpgrade/DistUpgradeCache.py: Make sure checkFreeSpace() still works for
    update-manager with its own implementation of MyCache.
  * DistUpgrade/DistUpgradeQuirks.py: Make sure snaps like core18 are not
    refreshed/installed from the stable/ubuntu-VERSION branch but instead use
    stable on upgrades. (LP: #1841225)

 -- Łukasz 'sil2100' Zemczak <lukasz.zemczak at ubuntu.com>  Mon, 09 Sep
2019 15:41:12 +0200

** Changed in: ubuntu-release-upgrader (Ubuntu Disco)
       Status: Fix Committed => Fix Released

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

Title:
  The disk-space-needed estimate doesn't account for the snaps

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Disco:
  Fix Released
Status in ubuntu-release-upgrader source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  Since there have been reports that users might fail to boot to a
  working gdm in the case of a full disk, we need to make sure users
  upgrading from and older release to disco/eoan have enough space for
  the upgrade to succeed. Currently we are installing snaps to replace
  certain debs on the system (+ refreshing existing snaps to newer
  channels/branches). The additional size required for the snap
  replacements was not taken into consideration when performing the
  upgrade, which might lead to edge-cases of users not having enough
  space for the upgrade to succeed.

  [Test Case]

  * Prepare a bionic machine
  * Make sure ubuntu-desktop and snapd are installed on it
  * Install core18 from stable and, for instance, gnome-characters from the stable/ubuntu-18.04 branch
  * Do snap list and snap refresh other gnome-related snaps to stable/ubuntu-18.04
  * Perform an upgrade to disco (with the --proposed option, to use disco-proposed)
  * Reboot
  * Make sure the update succeeded and all the installed gnome snaps now track stable/ubuntu-19.04 instead
  * Check /var/log/dist-upgrade/main.log and see if '/var' is listed in the calculated required space print-out

  Additional test case to make sure update-manager did not regress due
  to the changes:

  * On the newly upgraded system (or a new disco instance with ubuntu-release-upgrader upgraded to the version in disco-proposed), downgrade any of the installed packages
  * On the terminal, run `update-manager` and wait for the window to appear
  * Once the list of available upgrades appears, press the 'install now' button
  * Upgrades should install and no python traceback should be printed on the terminal

  [Regression Potential]

  As with any change touching the upgrade code-path, this change also carries a risk and should be well tested before going forward. That being said, the fix has been specifically basically limited to DistUpgradeQuirks to make regressions less likely. Additionally, unit tests have been added for every modified code-path.
  If any regressions should be found, the most likely place for those would be in size estimation, causing users to get notified of lack of space when they shouldn't. Another possible location would be all the things regarding replacing the debs with snaps - so either failures in snap replacement installation or refreshing.

  [Original Description]

  Looking at the code change recently made to install snaps on upgrade,
  it seems like there was no change made to the disk-space-estimate
  code. We had some reports recently that bionic might fail to boot to a
  working gdm on full disk so that could potentially be an important
  issue for upgraders

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