| 2019-06-27 15:50:45 |
Dan Streetman |
bug |
|
|
added bug |
| 2019-06-27 15:50:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-06-27 15:50:58 |
Dan Streetman |
bug task added |
|
lxd (Ubuntu Cosmic) |
|
| 2019-06-27 15:50:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-06-27 15:50:58 |
Dan Streetman |
bug task added |
|
lxd (Ubuntu Eoan) |
|
| 2019-06-27 15:50:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Disco |
|
| 2019-06-27 15:50:58 |
Dan Streetman |
bug task added |
|
lxd (Ubuntu Disco) |
|
| 2019-06-27 15:51:15 |
Dan Streetman |
lxd (Ubuntu Eoan): importance |
Undecided |
High |
|
| 2019-06-27 15:51:18 |
Dan Streetman |
lxd (Ubuntu Cosmic): importance |
Undecided |
High |
|
| 2019-06-27 15:51:21 |
Dan Streetman |
lxd (Ubuntu Disco): importance |
Undecided |
High |
|
| 2019-06-27 20:04:58 |
Dan Streetman |
description |
[impact]
a bionic system with lxd installed, when upgraded to cosmic or disco using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
in the bionic guest, make sure lxd is installed and configured.
run do-release-upgrade, which will stop at a warning prompt about lxd upgrade not being able to reach the snapstore.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade. |
[impact]
a bionic system with lxd installed, when upgraded to cosmic or disco using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
$ sudo apt install ubuntu-desktop
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
During upgrade, the normal prompts will be shown, which require Y or enter to continue. One of the early prompts indicates the snap store isn't reachable, and asks if you want to continue; choose Y to continue upgrading.
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists).
Abort continues the upgrade, after warning about the failure.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade. |
|
| 2019-06-27 20:07:21 |
Dan Streetman |
description |
[impact]
a bionic system with lxd installed, when upgraded to cosmic or disco using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
$ sudo apt install ubuntu-desktop
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
During upgrade, the normal prompts will be shown, which require Y or enter to continue. One of the early prompts indicates the snap store isn't reachable, and asks if you want to continue; choose Y to continue upgrading.
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists).
Abort continues the upgrade, after warning about the failure.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade. |
[impact]
a bionic system with lxd installed, when upgraded to cosmic or disco using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
$ sudo apt install ubuntu-desktop
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
During upgrade, the normal prompts will be shown, which require Y or enter to continue. One of the early prompts indicates the snap store isn't reachable, and asks if you want to continue; choose Y to continue upgrading.
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists). If lxd (and/or lxd-client) are installed but not configured (no /var/lib/lxd dir), skip can be chosen to continue the upgrade.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade. |
|
| 2019-06-27 20:13:08 |
Dan Streetman |
description |
[impact]
a bionic system with lxd installed, when upgraded to cosmic or disco using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
$ sudo apt install ubuntu-desktop
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
During upgrade, the normal prompts will be shown, which require Y or enter to continue. One of the early prompts indicates the snap store isn't reachable, and asks if you want to continue; choose Y to continue upgrading.
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists). If lxd (and/or lxd-client) are installed but not configured (no /var/lib/lxd dir), skip can be chosen to continue the upgrade.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade. |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
$ sudo apt install ubuntu-desktop
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
During upgrade, the normal prompts will be shown, which require Y or enter to continue. One of the early prompts indicates the snap store isn't reachable, and asks if you want to continue; choose Y to continue upgrading.
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists). If lxd (and/or lxd-client) are installed but not configured (no /var/lib/lxd dir), skip can be chosen to continue the upgrade.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
|
| 2019-06-27 20:14:09 |
Dan Streetman |
description |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
$ sudo apt install ubuntu-desktop
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
During upgrade, the normal prompts will be shown, which require Y or enter to continue. One of the early prompts indicates the snap store isn't reachable, and asks if you want to continue; choose Y to continue upgrading.
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists). If lxd (and/or lxd-client) are installed but not configured (no /var/lib/lxd dir), skip can be chosen to continue the upgrade.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
During upgrade, the normal prompts will be shown, which require Y or enter to continue. One of the early prompts indicates the snap store isn't reachable, and asks if you want to continue; choose Y to continue upgrading.
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists). If lxd (and/or lxd-client) are installed but not configured (no /var/lib/lxd dir), skip can be chosen to continue the upgrade.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
|
| 2019-06-27 20:24:45 |
Dan Streetman |
description |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
During upgrade, the normal prompts will be shown, which require Y or enter to continue. One of the early prompts indicates the snap store isn't reachable, and asks if you want to continue; choose Y to continue upgrading.
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists). If lxd (and/or lxd-client) are installed but not configured (no /var/lib/lxd dir), skip can be chosen to continue the upgrade.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists). If lxd (and/or lxd-client) are installed but not configured (no /var/lib/lxd dir), skip can be chosen to continue the upgrade.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
|
| 2019-06-27 20:26:39 |
Dan Streetman |
description |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd exists). If lxd (and/or lxd-client) are installed but not configured (no /var/lib/lxd dir), skip can be chosen to continue the upgrade.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits.
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd is populated). If lxd (and/or lxd-client) are installed but not configured, skip can be chosen to continue the upgrade, and after upgrade is complete, the lxd package will not be installed.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits; it is unclear if the system is in a good fully-upgraded state at this point (besides not having an upgraded lxd, of course).
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
|
| 2019-06-27 20:42:31 |
Dan Streetman |
description |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd is populated). If lxd (and/or lxd-client) are installed but not configured, skip can be chosen to continue the upgrade, and after upgrade is complete, the lxd package will not be installed.
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits; it is unclear if the system is in a good fully-upgraded state at this point (besides not having an upgraded lxd, of course).
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd is populated). If lxd (and/or lxd-client) are installed but not configured, skip can be chosen to continue the upgrade, and after upgrade is complete, the lxd package will not be installed. If skip is attempted when lxd has been initialized, this is shown:
--
Skipping is not allowed when LXD has been initialized
LXD appears to have been configured on this system. Please stop LXD and
remove local data in /var/lib/lxd/ if you would like to skip installing
the LXD snap and migrating the local data.
--
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits; it is unclear if the system is in a good fully-upgraded state at this point (besides not having an upgraded lxd, of course).
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
|
| 2019-06-27 20:43:55 |
Dan Streetman |
bug task added |
|
ubuntu-release-upgrader (Ubuntu) |
|
| 2019-06-27 20:46:42 |
Dan Streetman |
bug |
|
|
added subscriber Brian Murray |
| 2019-06-27 20:47:27 |
Dan Streetman |
bug |
|
|
added subscriber Stéphane Graber |
| 2019-06-27 20:49:32 |
Dan Streetman |
lxd (Ubuntu Eoan): importance |
High |
Undecided |
|
| 2019-06-27 20:49:34 |
Dan Streetman |
lxd (Ubuntu Disco): importance |
High |
Undecided |
|
| 2019-06-27 20:49:35 |
Dan Streetman |
lxd (Ubuntu Cosmic): importance |
High |
Undecided |
|
| 2019-06-27 20:51:24 |
Dan Streetman |
description |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd is populated). If lxd (and/or lxd-client) are installed but not configured, skip can be chosen to continue the upgrade, and after upgrade is complete, the lxd package will not be installed. If skip is attempted when lxd has been initialized, this is shown:
--
Skipping is not allowed when LXD has been initialized
LXD appears to have been configured on this system. Please stop LXD and
remove local data in /var/lib/lxd/ if you would like to skip installing
the LXD snap and migrating the local data.
--
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits; it is unclear if the system is in a good fully-upgraded state at this point (besides not having an upgraded lxd, of course).
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. |
[impact]
a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air-gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade.
[test case]
see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io)
-create VM using the bionic cloud image
-in the bionic guest:
$ sudo apt update
$ sudo apt dist-upgrade
-note: snapd and lxd should already be installed; verify this
$ dpkg -l |grep -E '^ii (lxd|snapd)'
ii lxd 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64 Container hypervisor based on LXC - client
ii snapd 2.39.2+18.04 amd64 Daemon and tooling that enable snap packages
-edit /etc/update-manager/release-upgrades to set Prompt=normal
-reboot, if needed due to kernel upgrade
-upgrade:
$ sudo do-release-upgrade
Once the upgrade reaches the lxd package, it will display:
--
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info lxd"
Aborting will cause the upgrade to fail and will require it to be re-
attempted once snapd is functional on the system.
Skipping will let the package upgrade continue but the LXD commands will
not be functional until the LXD snap is installed. Skipping is allowed
only when LXD is not activated on the system.
Unable to reach the snap store
--
With the possible choices of:
Retry
Abort
Skip
Retry, of course, will never succeed.
Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd is populated). If lxd (and/or lxd-client) are installed but not configured, skip can be chosen to continue the upgrade, and after upgrade is complete, the lxd package will not be installed. If skip is attempted when lxd has been initialized, this is shown:
--
Skipping is not allowed when LXD has been initialized
LXD appears to have been configured on this system. Please stop LXD and
remove local data in /var/lib/lxd/ if you would like to skip installing
the LXD snap and migrating the local data.
--
Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits; it is unclear if the system is in a good fully-upgraded state at this point (besides not having an upgraded lxd, of course).
[regression potential]
TBD
[other info]
this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade.
I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic.
This bug is unlikely to be seen by any enterprise customers right now, as most of them stick to LTS releases. However in 2020 once the LTS series 20.04 is released, some enterprise customers whose deployment is firewalled and/or airgapped may start to see this during upgrade. |
|
| 2019-06-28 12:14:35 |
Guilherme G. Piccoli |
bug |
|
|
added subscriber Guilherme G. Piccoli |
| 2019-06-28 16:13:12 |
Stéphane Graber |
lxd (Ubuntu Cosmic): status |
New |
Won't Fix |
|
| 2019-06-28 16:13:14 |
Stéphane Graber |
lxd (Ubuntu Disco): status |
New |
Won't Fix |
|
| 2019-06-28 16:13:16 |
Stéphane Graber |
lxd (Ubuntu Eoan): status |
New |
Won't Fix |
|
| 2019-06-30 23:43:54 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2019-09-24 20:03:02 |
Brian Murray |
tags |
|
rls-ee-incoming |
|
| 2019-10-03 15:20:16 |
Brian Murray |
tags |
rls-ee-incoming |
rls-ee-notfixing rls-ff-incoming |
|
| 2019-12-05 17:43:24 |
Brian Murray |
nominated for series |
|
Ubuntu Focal |
|
| 2019-12-05 17:43:24 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Focal) |
|
| 2019-12-05 17:43:24 |
Brian Murray |
bug task added |
|
lxd (Ubuntu Focal) |
|
| 2019-12-05 17:43:35 |
Brian Murray |
lxd (Ubuntu Focal): status |
New |
Won't Fix |
|
| 2019-12-05 17:43:52 |
Brian Murray |
tags |
rls-ee-notfixing rls-ff-incoming |
rls-ee-notfixing |
|
| 2019-12-20 19:24:08 |
Francis Ginther |
tags |
rls-ee-notfixing |
id-5de941ae648ff64e0f8f8e02 rls-ee-notfixing |
|
| 2020-01-23 09:14:31 |
Launchpad Janitor |
lxd (Ubuntu): status |
New |
Confirmed |
|
| 2020-01-23 09:14:31 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu): status |
New |
Confirmed |
|
| 2020-01-23 09:14:31 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Cosmic): status |
New |
Confirmed |
|
| 2020-01-23 09:14:31 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Disco): status |
New |
Confirmed |
|
| 2020-01-23 09:14:31 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Eoan): status |
New |
Confirmed |
|
| 2020-01-23 09:18:18 |
Christian Ehrhardt |
bug |
|
|
added subscriber Christian Ehrhardt |
| 2020-02-18 01:45:34 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Focal): status |
Confirmed |
Fix Released |
|
| 2020-02-19 21:34:23 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Eoan): status |
Confirmed |
Won't Fix |
|
| 2020-02-19 21:34:44 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Cosmic): status |
Confirmed |
Won't Fix |
|
| 2020-02-19 21:34:56 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Disco): status |
Confirmed |
Won't Fix |
|
| 2020-03-22 00:56:07 |
Stéphane Graber |
lxd (Ubuntu): status |
Confirmed |
Won't Fix |
|
| 2021-05-25 14:33:35 |
Patrick |
bug |
|
|
added subscriber Patrick |
