I just encountered this, attempting to upgrade 18.04 to 20.04. For me,
the problem is that I have an IPv6-only system, but api.snapcraft.io is
not reachable via IPv6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lxd (Ubuntu)
Status: Confirmed => Won't Fix
--
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
I tested an upgrade from 18.04 to 19.10 with lxd installed and access to
api.snapcraft.io blocked. When presented with the lxd installation
question I chose to abort, the upgrade completed and seemed fine. I then
reenabled access to api.snapcraft.io and ran 'dpkg --configure -a' (or
something
This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.12
---
ubuntu-release-upgrader (1:20.04.12) focal; urgency=medium
* data/release-upgrades: set Prompt to lts as focal is an LTS release.
* DistUpgrade/DistUpgradeQuirks.py: Do not allow the upgrade to proceed if
This breaks me quite often as well.
Even in cases where I "COULD" set up a httpproxy.
Let me add a showcase:
1. Bionic was fine, apt and software installs worked fine
E.g. the network was setup to allow the archive.ubuntu.com in the FW
But not for anything else (e.g. snapstore)
2.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxd (Ubuntu)
Status: New => Confirmed
--
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:
** Tags added: id-5de941ae648ff64e0f8f8e02
--
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
** Also affects: ubuntu-release-upgrader (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: lxd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: lxd (Ubuntu Focal)
Status: New => Won't Fix
** Tags removed: rls-ff-incoming
--
You
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing rls-ff-incoming
--
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
** Tags added: rls-ee-incoming
--
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
Hi,
Indeed, this is a won't fix for LXD as we are snap only at this point
and our preinst behavior is I believe correct in avoiding breaking
systems. The post-upgrade deb is completely empty so allowing the update
to proceed will completely break the existing LXD. The only options are
then
I suspect for lxd, this is likely a WontFix; for cosmic and later, it's
provided via snap, and unlikely to go back to a deb.
I targeted this against u-r-u as well, as the 'best' fix for this may be
to add a check at the start of the upgrade process, and let the upgrader
choose at that point what
> and let the upgrader choose at that point what to do
by 'upgrader' i meant the actual person doing the upgrade should be
notified, and choose what to do, before upgrade starts
** Changed in: lxd (Ubuntu Eoan)
Importance: High => Undecided
** Changed in: lxd (Ubuntu Disco)
Importance:
** 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,
** 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
19 matches
Mail list logo
