** Description changed:
[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.
+ -create VM using the bionic cloud image
+ -in the bionic guest:
+ $ sudo apt update
+ $ sudo apt dist-upgrade
+ $ sudo apt install ubuntu-desktop
- run do-release-upgrade, which will stop at a warning prompt about lxd
- upgrade not being able to reach the snapstore.
+ -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.
** Description changed:
[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.
+ 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).
+ 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, after warning about the failure.
-
+ 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.
** Description changed:
[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.
+ 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.
** Description changed:
[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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834501
Title:
do-release-upgrade from bionic->any disables lxd without snapstore
access
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1834501/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
