Chad, were you able to find the config that caused the effect? There is a
similar issue open here:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225
I am trying to find out if it is a regression or something in my config.
--
You received this bug notification because you are a
it seems we are running into something with network not being properly
setup in a lxc snapshot. The issue/feature for snapd.seed seems to be
that broken network configuration will result in snapd.seeded will wait
indefinitely on network connectivity. I'll file a separate bug if need
be with more
I'm wondering if we are seeing a regression here. On a focal host
system, I am unable to launch disco or eoan containers as snapd.seeded
service doesn't complete:
root@mytest:~# systemd-analyze
Bootup is not yet finished
(org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try
>From within the container:
$ snap changes
1Error today at 20:00 UTC today at 20:00 UTC Initialize system state
2Error today at 20:00 UTC today at 20:00 UTC Initialize device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806070
Title:
snapd.seeded.service never completes preventing full boot to default
That's great to know, thank you!
** Changed in: snapd
Status: Triaged => Confirmed
** Changed in: snapd
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@zyga, I'm happy to report the -proposed version fixed this bug and also
allowed all my snap to be refreshed. Thanks for all your help, I really
appreciate!
$ sudo apt-get install snapd
...
The following packages will be upgraded:
snapd (2.34.2+18.04 => 2.35.5+18.04)
$ snap version
snap
Dear reporter, can you please try to install the snapd package from the
-proposed pocket. If this resolves the issue we will conclude it was the
deadlock problem described above. We need ensure that the SRU is
released so that everyone affected can update snapd using the classic
package.
--
You
We have a suspicion this is a bug that was fixed and released via core
snap but not released via SRU. Possible PRs
https://github.com/snapcore/snapd/pull/5827 and
https://github.com/snapcore/snapd/pull/6027
Upon aborting and re-trying seeding we see:
https://paste.ubuntu.com/p/pM2bBdqH5w/ with
from the output of "snap tasks 31" it looks like that change requested
snapd to restart but that never happened which is unexpected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806070
Title:
** Attachment added: "'snap tasks 31' output"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1806070/+attachment/5222005/+files/snap-tasks-31.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
mmh, given that, what does "snap tasks 31" shows?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806070
Title:
snapd.seeded.service never completes preventing full boot to default
target
To
@pedronis:
$ snap changes
ID Status Spawn Ready Summary
31 Doing 2 days ago, at 09:31 EST - Initialize system state
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "snapd's state.json"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1806070/+attachment/5222003/+files/snapd-state.json.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just realized now that this issue is preventing snap from refreshing
all my snaps:
$ sudo snap refresh lxd
error: cannot refresh "lxd": snap "lxd" has "seed" change in progress
An example of this is that lxd is stuck at version 3.2 while it should
be at 3.7:
$ snap info lxd | sed -n
what does "snap changes" says on such a system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806070
Title:
snapd.seeded.service never completes preventing full boot to default
target
To manage
17 matches
Mail list logo
