| 2017-10-31 01:33:31 |
James |
bug |
|
|
added bug |
| 2017-10-31 04:34:48 |
Ubuntu Foundations Team Bug Bot |
tags |
|
bot-comment |
|
| 2017-10-31 15:03:06 |
Brian Murray |
affects |
ubuntu |
ubuntu-release-upgrader (Ubuntu) |
|
| 2017-10-31 15:03:39 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): status |
New |
Incomplete |
|
| 2017-10-31 15:03:48 |
Brian Murray |
bug |
|
|
added subscriber Brian Murray |
| 2017-11-07 01:32:36 |
Travis |
attachment added |
|
main.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1728760/+attachment/5005083/+files/main.log |
|
| 2017-11-07 03:16:52 |
James |
attachment added |
|
apt.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1728760/+attachment/5005104/+files/apt.log |
|
| 2017-11-07 03:17:13 |
James |
attachment added |
|
apt-term.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1728760/+attachment/5005105/+files/apt-term.log |
|
| 2017-11-07 03:17:38 |
James |
attachment added |
|
history.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1728760/+attachment/5005106/+files/history.log |
|
| 2017-11-07 03:17:55 |
James |
attachment added |
|
main.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1728760/+attachment/5005107/+files/main.log |
|
| 2017-11-07 18:39:18 |
Brian Murray |
summary |
17.04 to 17.10 dist upgrade automatically switched me to lowlatency kernel |
17.04 to 17.10 dist upgrade switched me to lowlatency kernel b/c of aufs-tools |
|
| 2017-11-07 18:39:24 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2017-11-07 18:39:29 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-11-07 19:02:01 |
Steve Langasek |
ubuntu-release-upgrader (Ubuntu): importance |
Medium |
Critical |
|
| 2017-11-07 19:07:39 |
Steve Langasek |
description |
When I upgraded from 17.04 to 17.10, I was automatically switched from the generic kernel to the lowlatency kernel. I did not have the lowlatency kernel installed prior to the dist upgrade (I have verified this by inspecting my /var/log/apt/history.log* files, all upgrades prior to the dist upgrade only show updating *-generic kernel packages, if I had lowlatency installed it would show that as well.) I'm not sure why I was switched to lowlatency, I don't see anything in the release notes saying that there was a switch to lowlatency as the default, and other users who have just done a dist upgrade weren't switched to lowlatency. So I think it is probably a bug that I was switched to lowlatency - perhaps there's a package that I have installed that is incorrectly depending on the lowlatency kernel in 17.10? I'm not sure how to find out if that's the case.
To be explicit, after the dist-upgrade, I had both the 4.13.0-16-generic and 4.13.0-16-lowlatency kernels installed, and by default 4.13.0-16-lowlatency was what was booted into.
This also caused a problem when I did the upgrade - perhaps this is a separate bug that I should report, let me know and I'll do that. After the dist-upgrade, wifi didn't work. I have a BCM4352 wifi card, whose driver is provided by the bcmwl-kernel-source package, which uses DKMS to compile it. Presumably during the dist-upgrade, the driver was compiled for the 4.13.0-16-generic kernel, so when I manually selected that kernel on boot, it worked, but it wasn't compiled for the 4.13.0-16-lowlatency kernel, which is why wifi didn't work out of the box after the dist-upgrade. The solution was of course straight forward, I had to reinstall the bcmwl-kernel-source package, but a non working system after an upgrade requiring reinstalling packages or booting into a different kernel to fix is presumably a bug.
If the switch from generic to lowlatency was a feature, not a bug, then such a switch should also be accompanied by compiling all the kernel modules that were compiled against the generic kernel against the new lowlatency kernel, so as to ensure the system is in a working state after completing a dist upgrade. Also, if the switch is a feature, then I would expect it to be documented in the release notes with a brief explanation or link to more information on why the switch was done. |
[SRU Justification]
The combination in 17.10 of a new Recommends: on aufs-dkms from aufs-tools, with a new Provides: aufs-dkms on each of the kernel packages causes apt to choose a kernel at random to satisfy this package relationship on upgrade from 17.04.
Randomly installing a kernel is bad mmmkay.
[Test case]
1. Install aufs-tools and linux-image-generic on a 17.04 system.
2. Configure the apt sources to point to artful.
3. Run sudo apt update && sudo apt dist-upgrade.
4. Confirm that apt wants to install linux-image-4.13.0-16-lowlatency.
5. Cancel the upgrade.
6. Enable artful-proposed in sources.list.
7. Run sudo apt update && sudo apt dist-upgrade.
8. Confirm that apt no longer offers to install linux-image-4.13.0-16-lowlatency.
[Original description]
When I upgraded from 17.04 to 17.10, I was automatically switched from the generic kernel to the lowlatency kernel. I did not have the lowlatency kernel installed prior to the dist upgrade (I have verified this by inspecting my /var/log/apt/history.log* files, all upgrades prior to the dist upgrade only show updating *-generic kernel packages, if I had lowlatency installed it would show that as well.) I'm not sure why I was switched to lowlatency, I don't see anything in the release notes saying that there was a switch to lowlatency as the default, and other users who have just done a dist upgrade weren't switched to lowlatency. So I think it is probably a bug that I was switched to lowlatency - perhaps there's a package that I have installed that is incorrectly depending on the lowlatency kernel in 17.10? I'm not sure how to find out if that's the case.
To be explicit, after the dist-upgrade, I had both the 4.13.0-16-generic and 4.13.0-16-lowlatency kernels installed, and by default 4.13.0-16-lowlatency was what was booted into.
This also caused a problem when I did the upgrade - perhaps this is a separate bug that I should report, let me know and I'll do that. After the dist-upgrade, wifi didn't work. I have a BCM4352 wifi card, whose driver is provided by the bcmwl-kernel-source package, which uses DKMS to compile it. Presumably during the dist-upgrade, the driver was compiled for the 4.13.0-16-generic kernel, so when I manually selected that kernel on boot, it worked, but it wasn't compiled for the 4.13.0-16-lowlatency kernel, which is why wifi didn't work out of the box after the dist-upgrade. The solution was of course straight forward, I had to reinstall the bcmwl-kernel-source package, but a non working system after an upgrade requiring reinstalling packages or booting into a different kernel to fix is presumably a bug.
If the switch from generic to lowlatency was a feature, not a bug, then such a switch should also be accompanied by compiling all the kernel modules that were compiled against the generic kernel against the new lowlatency kernel, so as to ensure the system is in a working state after completing a dist upgrade. Also, if the switch is a feature, then I would expect it to be documented in the release notes with a brief explanation or link to more information on why the switch was done. |
|
| 2017-11-07 19:11:12 |
Steve Langasek |
description |
[SRU Justification]
The combination in 17.10 of a new Recommends: on aufs-dkms from aufs-tools, with a new Provides: aufs-dkms on each of the kernel packages causes apt to choose a kernel at random to satisfy this package relationship on upgrade from 17.04.
Randomly installing a kernel is bad mmmkay.
[Test case]
1. Install aufs-tools and linux-image-generic on a 17.04 system.
2. Configure the apt sources to point to artful.
3. Run sudo apt update && sudo apt dist-upgrade.
4. Confirm that apt wants to install linux-image-4.13.0-16-lowlatency.
5. Cancel the upgrade.
6. Enable artful-proposed in sources.list.
7. Run sudo apt update && sudo apt dist-upgrade.
8. Confirm that apt no longer offers to install linux-image-4.13.0-16-lowlatency.
[Original description]
When I upgraded from 17.04 to 17.10, I was automatically switched from the generic kernel to the lowlatency kernel. I did not have the lowlatency kernel installed prior to the dist upgrade (I have verified this by inspecting my /var/log/apt/history.log* files, all upgrades prior to the dist upgrade only show updating *-generic kernel packages, if I had lowlatency installed it would show that as well.) I'm not sure why I was switched to lowlatency, I don't see anything in the release notes saying that there was a switch to lowlatency as the default, and other users who have just done a dist upgrade weren't switched to lowlatency. So I think it is probably a bug that I was switched to lowlatency - perhaps there's a package that I have installed that is incorrectly depending on the lowlatency kernel in 17.10? I'm not sure how to find out if that's the case.
To be explicit, after the dist-upgrade, I had both the 4.13.0-16-generic and 4.13.0-16-lowlatency kernels installed, and by default 4.13.0-16-lowlatency was what was booted into.
This also caused a problem when I did the upgrade - perhaps this is a separate bug that I should report, let me know and I'll do that. After the dist-upgrade, wifi didn't work. I have a BCM4352 wifi card, whose driver is provided by the bcmwl-kernel-source package, which uses DKMS to compile it. Presumably during the dist-upgrade, the driver was compiled for the 4.13.0-16-generic kernel, so when I manually selected that kernel on boot, it worked, but it wasn't compiled for the 4.13.0-16-lowlatency kernel, which is why wifi didn't work out of the box after the dist-upgrade. The solution was of course straight forward, I had to reinstall the bcmwl-kernel-source package, but a non working system after an upgrade requiring reinstalling packages or booting into a different kernel to fix is presumably a bug.
If the switch from generic to lowlatency was a feature, not a bug, then such a switch should also be accompanied by compiling all the kernel modules that were compiled against the generic kernel against the new lowlatency kernel, so as to ensure the system is in a working state after completing a dist upgrade. Also, if the switch is a feature, then I would expect it to be documented in the release notes with a brief explanation or link to more information on why the switch was done. |
[SRU Justification]
The combination in 17.10 of a new Recommends: on aufs-dkms from aufs-tools, with a new Provides: aufs-dkms on each of the kernel packages causes apt to choose a kernel at random to satisfy this package relationship on upgrade from 17.04.
Randomly installing a kernel is bad mmmkay.
[Test case]
1. Install aufs-tools and linux-image-generic on a 17.04 system.
2. Configure the apt sources to point to artful.
3. Run sudo apt update && sudo apt dist-upgrade.
4. Confirm that apt wants to install linux-image-4.13.0-16-lowlatency.
5. Cancel the upgrade.
6. Enable artful-proposed in sources.list.
7. Run sudo apt update && sudo apt dist-upgrade.
8. Confirm that apt no longer offers to install linux-image-4.13.0-16-lowlatency.
[Regression potential]
This will cause a behavior change in that currently, installing aufs-tools into a chroot or container will pull in a kernel package with it by default, and after this SRU it will no longer do so.
This is not a regression.
If a user is running a non-Ubuntu kernel which does not provide (explicitly or logically) aufs-dkms, after this SRU, installing aufs-tools will not cause an Ubuntu kernel package to be pulled in as a recommends.
This is uninteresting, as the user would discover the lack of kernel aufs support the first time they tried to use the utilities; and it is unlikely that their preferred solution to the problem would be to stop using a non-Ubuntu kernel.
[Original description]
When I upgraded from 17.04 to 17.10, I was automatically switched from the generic kernel to the lowlatency kernel. I did not have the lowlatency kernel installed prior to the dist upgrade (I have verified this by inspecting my /var/log/apt/history.log* files, all upgrades prior to the dist upgrade only show updating *-generic kernel packages, if I had lowlatency installed it would show that as well.) I'm not sure why I was switched to lowlatency, I don't see anything in the release notes saying that there was a switch to lowlatency as the default, and other users who have just done a dist upgrade weren't switched to lowlatency. So I think it is probably a bug that I was switched to lowlatency - perhaps there's a package that I have installed that is incorrectly depending on the lowlatency kernel in 17.10? I'm not sure how to find out if that's the case.
To be explicit, after the dist-upgrade, I had both the 4.13.0-16-generic and 4.13.0-16-lowlatency kernels installed, and by default 4.13.0-16-lowlatency was what was booted into.
This also caused a problem when I did the upgrade - perhaps this is a separate bug that I should report, let me know and I'll do that. After the dist-upgrade, wifi didn't work. I have a BCM4352 wifi card, whose driver is provided by the bcmwl-kernel-source package, which uses DKMS to compile it. Presumably during the dist-upgrade, the driver was compiled for the 4.13.0-16-generic kernel, so when I manually selected that kernel on boot, it worked, but it wasn't compiled for the 4.13.0-16-lowlatency kernel, which is why wifi didn't work out of the box after the dist-upgrade. The solution was of course straight forward, I had to reinstall the bcmwl-kernel-source package, but a non working system after an upgrade requiring reinstalling packages or booting into a different kernel to fix is presumably a bug.
If the switch from generic to lowlatency was a feature, not a bug, then such a switch should also be accompanied by compiling all the kernel modules that were compiled against the generic kernel against the new lowlatency kernel, so as to ensure the system is in a working state after completing a dist upgrade. Also, if the switch is a feature, then I would expect it to be documented in the release notes with a brief explanation or link to more information on why the switch was done. |
|
| 2017-11-07 19:21:27 |
Steve Langasek |
ubuntu-release-upgrader (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2017-11-07 19:21:37 |
Steve Langasek |
affects |
ubuntu-release-upgrader (Ubuntu) |
aufs-tools (Ubuntu) |
|
| 2017-11-07 19:25:28 |
Brian Murray |
nominated for series |
|
Ubuntu Artful |
|
| 2017-11-07 19:25:28 |
Brian Murray |
bug task added |
|
aufs-tools (Ubuntu Artful) |
|
| 2017-11-07 19:30:38 |
Brian Murray |
aufs-tools (Ubuntu Artful): status |
New |
Fix Committed |
|
| 2017-11-07 19:30:40 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-11-07 19:30:43 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-11-07 19:30:47 |
Brian Murray |
tags |
bot-comment |
bot-comment verification-needed verification-needed-artful |
|
| 2017-11-16 16:04:44 |
Jesse Glick |
bug |
|
|
added subscriber Jesse Glick |
| 2017-11-16 21:24:30 |
Brian Murray |
tags |
bot-comment verification-needed verification-needed-artful |
bot-comment verification-done verification-done-artful |
|
| 2017-11-17 00:01:32 |
Launchpad Janitor |
aufs-tools (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2017-11-17 00:01:36 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-05-01 13:19:44 |
Jaroslavas Karmazinas |
aufs-tools (Ubuntu): assignee |
|
Jaroslavas Karmazinas (cheops) |
|
| 2020-05-01 13:19:46 |
Jaroslavas Karmazinas |
aufs-tools (Ubuntu Artful): assignee |
|
Jaroslavas Karmazinas (cheops) |
|
| 2020-05-01 13:19:55 |
Jaroslavas Karmazinas |
aufs-tools (Ubuntu): status |
Fix Committed |
Incomplete |
|
| 2020-05-01 13:19:59 |
Jaroslavas Karmazinas |
aufs-tools (Ubuntu): status |
Incomplete |
Opinion |
|
| 2020-05-01 13:20:02 |
Jaroslavas Karmazinas |
aufs-tools (Ubuntu): status |
Opinion |
Confirmed |
|
| 2020-05-01 13:20:15 |
Jaroslavas Karmazinas |
aufs-tools (Ubuntu): assignee |
Jaroslavas Karmazinas (cheops) |
|
|
| 2020-05-01 13:20:18 |
Jaroslavas Karmazinas |
aufs-tools (Ubuntu): assignee |
|
Jaroslavas Karmazinas (cheops) |
|
| 2020-05-01 15:38:39 |
Jaroslavas Karmazinas |
bug |
|
|
added subscriber Jaroslavas Karmazinas |
| 2020-07-14 13:36:33 |
Ioana Lasc |
aufs-tools (Ubuntu): assignee |
Jaroslavas Karmazinas (cheops) |
|
|
| 2020-07-14 13:36:38 |
Ioana Lasc |
aufs-tools (Ubuntu Artful): assignee |
Jaroslavas Karmazinas (cheops) |
|
|
