| 2018-08-02 17:27:37 |
Brian Murray |
bug |
|
|
added bug |
| 2018-08-02 17:27:49 |
Brian Murray |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-08-02 17:27:49 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Bionic) |
|
| 2018-08-02 17:28:01 |
Brian Murray |
summary |
dist-upgrader does not clean up downloaded debs |
dist-upgrader should clean up downloaded debs |
|
| 2018-08-02 17:29:06 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): status |
New |
Fix Released |
|
| 2018-08-02 17:31:45 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Bionic): status |
New |
In Progress |
|
| 2018-08-02 17:31:49 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2018-08-02 17:31:52 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Bionic): assignee |
|
Brian Murray (brian-murray) |
|
| 2018-08-02 19:05:34 |
Brian Murray |
description |
During the release upgrade process packages for the new release are downloaded to the apt configuration "Dir::Cache::archives" (usually /var/cache/apt/archives/), but those are not removed from disk until some time later. With the dist-upgrader growing support for transitioning from debian packages to snaps for some software it's possible that there may not be enough free space on disk (as the upgrader doesn't currently calculate the space need which is bug 1783597) to support installing the snaps. Subsequently, it'd be good to remove the debs from disk after the upgrade has completed since they are likely on /var which is where the snaps will need space.
[Test Case]
1) Run 'du -sh /var/cache/apt/archives'
2) Upgrade from Ubuntu 16.04 to Ubuntu 18.04
3) Run 'du -sh /var/cache/apt/archives'
4) Observe that /var/cache/apt/archives is taking up more space than it id.
With the version of the dist-upgrader in -proposed /var/cache/apt/archives should be nearly empty some debs may be left because they are left over from regular updates in Ubuntu 16.04 and were not part of the release upgrade process.
[Regression Potential]
It's possible that the debs are removed too early and if there were a failure to upgrade it'd be hard to recover from. One way to test this would be to use the apt-clone file from 1766890 which would create an upgrade failure. |
During the release upgrade process packages for the new release are downloaded to the apt configuration "Dir::Cache::archives" (usually /var/cache/apt/archives/), but those are not removed from disk until some time later. With the dist-upgrader growing support for transitioning from debian packages to snaps for some software it's possible that there may not be enough free space on disk (as the upgrader doesn't currently calculate the space need which is bug 1783597) to support installing the snaps. Subsequently, it'd be good to remove the debs from disk after the upgrade has completed since they are likely on /var which is where the snaps will need space.
[Test Case]
1) Run 'du -sh /var/cache/apt/archives'
2) Upgrade from Ubuntu 16.04 to Ubuntu 18.04
3) Run 'du -sh /var/cache/apt/archives'
4) Observe that /var/cache/apt/archives is taking up more space than it did.
With the version of the dist-upgrader in -proposed /var/cache/apt/archives should be nearly empty some debs may be left because they are left over from regular updates in Ubuntu 16.04 and were not part of the release upgrade process.
[Regression Potential]
It's possible that the debs are removed too early and if there were a failure to upgrade it'd be hard to recover from. One way to test this would be to use the apt-clone file from 1766890 which would create an upgrade failure. |
|
| 2018-08-02 19:05:57 |
Brian Murray |
description |
During the release upgrade process packages for the new release are downloaded to the apt configuration "Dir::Cache::archives" (usually /var/cache/apt/archives/), but those are not removed from disk until some time later. With the dist-upgrader growing support for transitioning from debian packages to snaps for some software it's possible that there may not be enough free space on disk (as the upgrader doesn't currently calculate the space need which is bug 1783597) to support installing the snaps. Subsequently, it'd be good to remove the debs from disk after the upgrade has completed since they are likely on /var which is where the snaps will need space.
[Test Case]
1) Run 'du -sh /var/cache/apt/archives'
2) Upgrade from Ubuntu 16.04 to Ubuntu 18.04
3) Run 'du -sh /var/cache/apt/archives'
4) Observe that /var/cache/apt/archives is taking up more space than it did.
With the version of the dist-upgrader in -proposed /var/cache/apt/archives should be nearly empty some debs may be left because they are left over from regular updates in Ubuntu 16.04 and were not part of the release upgrade process.
[Regression Potential]
It's possible that the debs are removed too early and if there were a failure to upgrade it'd be hard to recover from. One way to test this would be to use the apt-clone file from 1766890 which would create an upgrade failure. |
During the release upgrade process packages for the new release are downloaded to the apt configuration "Dir::Cache::archives" (usually /var/cache/apt/archives/), but those are not removed from disk until some time later. With the dist-upgrader growing support for transitioning from debian packages to snaps for some software it's possible that there may not be enough free space on disk (as the upgrader doesn't currently calculate the space need which is bug 1783597) to support installing the snaps. Subsequently, it'd be good to remove the debs from disk after the upgrade has completed since they are likely on /var which is where the snaps will need space.
[Test Case]
1) Run 'du -sh /var/cache/apt/archives'
2) Upgrade from Ubuntu 16.04 to Ubuntu 18.04
3) Run 'du -sh /var/cache/apt/archives'
4) Observe that /var/cache/apt/archives is taking up more space than it did.
With the version of the dist-upgrader in -proposed /var/cache/apt/archives should be nearly empty - some debs may be left because they are left over from regular updates in Ubuntu 16.04 and were not part of the release upgrade process.
[Regression Potential]
It's possible that the debs are removed too early and if there were a failure to upgrade it'd be hard to recover from. One way to test this would be to use the apt-clone file from 1766890 which would create an upgrade failure. |
|
| 2018-08-06 15:52:22 |
Łukasz Zemczak |
ubuntu-release-upgrader (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-08-06 15:52:23 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-08-06 15:52:24 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-08-06 15:52:27 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-08-06 19:35:58 |
Brian Murray |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
| 2018-08-09 15:23:55 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-08-09 15:24:11 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
