| 2019-03-27 13:20:22 |
Balint Reczey |
bug |
|
|
added bug |
| 2019-03-27 13:20:46 |
Balint Reczey |
bug |
|
|
added subscriber Michael Hudson-Doyle |
| 2019-03-27 18:14:43 |
Stéphane Graber |
lxd (Ubuntu): status |
New |
Won't Fix |
|
| 2019-03-27 20:07:42 |
Stéphane Graber |
lxd (Ubuntu): status |
Won't Fix |
Triaged |
|
| 2019-03-27 20:07:44 |
Stéphane Graber |
lxd (Ubuntu): importance |
Undecided |
Low |
|
| 2019-03-28 12:21:29 |
Francis Ginther |
tags |
|
id-5c9b7900c475da3728353b23 |
|
| 2019-03-28 12:37:48 |
Francis Ginther |
tags |
id-5c9b7900c475da3728353b23 |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 |
|
| 2019-03-28 23:35:40 |
Balint Reczey |
description |
Upgrading from Bionic to Cosmic (or later) is not possible in WSL (https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux) fails since when lxd package upgrade (with the deb -> snap transition) starts it can't be completed successfully. The package upgrade can only be aborted if the snap command fails, hence the distribution upgrade can't be completed either.
As a workaround one can do:
$ sudo mv /usr/bin/snap /usr/bin/snap.real
$ sudo ln -s /bin/true /usr/bin/snap
in a separate terminal, but this is not a smooth upgrade experience by any means.
The upgrade can fail the same way if the snap store is not available possibly due to strict firewalling requirements and most likely distro upgrades should work in those environments as well.
As a solution when the snap transition does not work during the package upgrade please upgrade the package to a state, where new invocations of lxd or lxc starts the snap installation later.
A prototype can be found here:
https://code.launchpad.net/~mwhudson/+git/lxd-installer/+ref/master |
Upgrading from Bionic to Cosmic (or later) is not possible in WSL (https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux) since when lxd package upgrade (with the deb -> snap transition) starts it can't be completed successfully. The package upgrade can only be aborted if the snap command fails, hence the distribution upgrade can't be completed either.
As a workaround one can do:
$ sudo mv /usr/bin/snap /usr/bin/snap.real
$ sudo ln -s /bin/true /usr/bin/snap
in a separate terminal, but this is not a smooth upgrade experience by any means.
The upgrade can fail the same way if the snap store is not available possibly due to strict firewalling requirements and most likely distro upgrades should work in those environments as well.
As a solution when the snap transition does not work during the package upgrade please upgrade the package to a state, where new invocations of lxd or lxc starts the snap installation later.
A prototype can be found here:
https://code.launchpad.net/~mwhudson/+git/lxd-installer/+ref/master |
|
| 2019-04-05 16:13:53 |
Balint Reczey |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-04-05 16:13:53 |
Balint Reczey |
bug task added |
|
lxd (Ubuntu Cosmic) |
|
| 2019-04-05 16:32:53 |
Stéphane Graber |
lxd (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-04-05 16:32:56 |
Stéphane Graber |
lxd (Ubuntu Cosmic): status |
Triaged |
In Progress |
|
| 2019-04-05 16:33:00 |
Stéphane Graber |
lxd (Ubuntu Cosmic): assignee |
|
Stéphane Graber (stgraber) |
|
| 2019-04-05 16:33:03 |
Stéphane Graber |
lxd (Ubuntu): assignee |
|
Stéphane Graber (stgraber) |
|
| 2019-04-05 16:33:05 |
Stéphane Graber |
lxd (Ubuntu Cosmic): importance |
Undecided |
Low |
|
| 2019-04-05 16:33:08 |
Stéphane Graber |
lxd (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2019-04-06 00:05:04 |
Launchpad Janitor |
lxd (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2019-04-06 18:04:58 |
Balint Reczey |
description |
Upgrading from Bionic to Cosmic (or later) is not possible in WSL (https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux) since when lxd package upgrade (with the deb -> snap transition) starts it can't be completed successfully. The package upgrade can only be aborted if the snap command fails, hence the distribution upgrade can't be completed either.
As a workaround one can do:
$ sudo mv /usr/bin/snap /usr/bin/snap.real
$ sudo ln -s /bin/true /usr/bin/snap
in a separate terminal, but this is not a smooth upgrade experience by any means.
The upgrade can fail the same way if the snap store is not available possibly due to strict firewalling requirements and most likely distro upgrades should work in those environments as well.
As a solution when the snap transition does not work during the package upgrade please upgrade the package to a state, where new invocations of lxd or lxc starts the snap installation later.
A prototype can be found here:
https://code.launchpad.net/~mwhudson/+git/lxd-installer/+ref/master |
[Impact]
* Upgrading .deb-packaged lxd to the lxd .deb package that just installs the snap fails when the lxd snap can't be installed.
* This breaks package upgrades and specifically do-release-upgrade in the middle of the release upgrade.
* The fix lets skipping the installation of the lxd snap if lxd has not been activated on the system.
[Test Case]
1.
* Install the Ubuntu 18.04 app from the Microsoft Store on Windows 10
* Upgrade the packages to the latest versions in 18.04
* Make sure the lxd package is installed
* Run sudo do-release-upgrade
* Observe the release upgrade failing without the fix and offering skipping the snap installation and then succeeding after skipping it.
* Observe the lxd package still being installed but the lxc and lxd commands asking for installing the lxd snap
* Pretend that there is an activated lxd server:
# mkdir /var/lib/lxd
# touch /var/lib/lxd/server.crt
* Reinstall the lxd package
# apt-get install --reinstall lxd
* Observe the installation not allowing to skip the installation of the lxd snap. (By removing the created file skipping can be made allowed again.)
2.
* On a fully upgraded cosmic system install the previous version of the package, then upgrade to the fixed version.
* Observe the upgrade succeeding
3.
* On a fully upgraded cosmic system install the fixed version of the package, then remove the lxd snap.
* Observe the lxc and lxd commands asking for installing the lxd snap.
4.
* On a fully upgraded cosmic system purge the lxd packge and remove the lxd snap.
* Install the fixed package and observe it installing the lxd snap as well.
[Regression Potential]
* The fix includes changing the packaged-shipped lxc and lxd commands to print an error message if the lxd snap is missing. This is very simple and unlikely to cause regressions.
* The change to the package's prerm script is more extensive and in case of a programming error error it may cause upgrade/installation failures. The provided tests excercise the
[Original Bug Text]
Upgrading from Bionic to Cosmic (or later) is not possible in WSL (https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux) since when lxd package upgrade (with the deb -> snap transition) starts it can't be completed successfully. The package upgrade can only be aborted if the snap command fails, hence the distribution upgrade can't be completed either.
As a workaround one can do:
$ sudo mv /usr/bin/snap /usr/bin/snap.real
$ sudo ln -s /bin/true /usr/bin/snap
in a separate terminal, but this is not a smooth upgrade experience by any means.
The upgrade can fail the same way if the snap store is not available possibly due to strict firewalling requirements and most likely distro upgrades should work in those environments as well.
As a solution when the snap transition does not work during the package upgrade please upgrade the package to a state, where new invocations of lxd or lxc starts the snap installation later.
A prototype can be found here:
https://code.launchpad.net/~mwhudson/+git/lxd-installer/+ref/master |
|
| 2019-04-08 13:09:16 |
Łukasz Zemczak |
lxd (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2019-04-08 13:09:18 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-04-08 13:09:19 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2019-04-08 13:09:22 |
Łukasz Zemczak |
tags |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 verification-needed verification-needed-cosmic |
|
| 2019-04-10 12:23:45 |
Francis Ginther |
tags |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 verification-needed verification-needed-cosmic |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d verification-needed verification-needed-cosmic |
|
| 2019-04-11 09:00:12 |
Balint Reczey |
tags |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d verification-needed verification-needed-cosmic |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d verification-failed verification-failed-cosmic |
|
| 2019-04-23 18:08:35 |
Brian Murray |
tags |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d verification-failed verification-failed-cosmic |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d verification-needed verification-needed-cosmic |
|
| 2019-04-24 12:48:47 |
Francis Ginther |
tags |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d verification-needed verification-needed-cosmic |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d id-5cc028d1039e9572f93b3f1e verification-needed verification-needed-cosmic |
|
| 2019-04-30 09:58:31 |
Balint Reczey |
tags |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d id-5cc028d1039e9572f93b3f1e verification-needed verification-needed-cosmic |
id-5c536653f083fd53e3c3deaf id-5c9b7900c475da3728353b23 id-5cad1e2aa0db9c596d15215d id-5cc028d1039e9572f93b3f1e verification-done verification-done-cosmic |
|
| 2019-05-02 20:25:25 |
Launchpad Janitor |
lxd (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-05-02 20:25:29 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
