Have confirmed the packages to be functional on both focal and impish.
Tried installation, upgrade and basic container creation, deletion and normal
operations.
** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish
Hello,
We usually prefer for support questions to be asked at
https://discuss.linuxcontainers.org and issues be filed at
https://github.com/lxc/lxd/issues.
We only really look at Launchpad for bugs in the LXD deb which these
days is limited to Ubuntu 18.04 as everything afterwards is using the
For nvidia.runtime=true to work, you need an NVIDIA driver as well as
the CUDA library on the host.
The libnvidia-container part is identical on both architectures and has
been used by Anbox before, so we're pretty confident it works. Just not
on 22.04 hosts.
--
You received this bug
Right, nvidia-container-cli is specifically designed to use files from
the host (outside of snap environment) as the files it loads (through
dlopen) cannot be bundled (cuda, driver files, ...).
nvidia-container-cli has logic to effectively chroot prior to processing any of
the dlopen.
It's then
Can you show:
- cat /proc/self/cgroup
- cat /proc/self/mounts
On a broken system?
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971571
stgraber@dakara:~$ lxc snapshot does-not-exist snap0
Error: Instance not found
** Changed in: lxd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lxd (Ubuntu)
Status: In Progress => 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/1964833
Title:
Disable "latest" as upgrade option on focal
To manage
`images:` never had any riscv64 image. When that happens, the image
selector downloads the closest image available which in this case is an
amd64 image.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is normal behavior when no image can be found for the local
architecture.
images: doesn't have any riscv64 images.
ubuntu: only has 21.10
ubuntu-daily: has 22.04
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Public bug reported:
LXC 5.0 LTS will very soon be released.
The upstream release has been held up due to an incomplete port to meson (and
deprecation of autotools), it's otherwise been ready to go for a few months.
As far as LXC releases go, it's a very light one. Comparing it to
current
The verification of the Stable Release Update for lxd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for lxd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Ah yeah, that could be. I figured I'd test what's in -proposed but if
-proposed is a security only fix on top of -37, that wouldn't help much.
It's a bit frustrating because users would have gotten the busted kernel
as part of -37 which includes a security fix but then the only real
option to get
This repeats in a loop and fills tens of GBs of space with kernel logs
in just a few minutes before crashing the entire system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966499
Title:
Recent
Mar 25 16:18:30 abydos kernel: [ 1319.549186] [ cut here
]
Mar 25 16:18:30 abydos kernel: [ 1319.549191] WARNING: CPU: 12 PID: 15052 at
arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9f/0xc0 [kvm_intel]
Mar 25 16:18:30 abydos kernel: [ 1319.549213] Modules linked in:
Public bug reported:
Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers
as they hit:
https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55
It looks like we need to get e90e51d5f01d included in those
Uploaded to the queue
** Changed in: lxd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959047
Title:
systemd ignores RootDirectory option
Okay, that looks promising. Can you add the SRU sections to the
description describing those testing steps? Then I can upload to the SRU
queue referencing this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adding linux-kvm to the bug. It looks like if we can have the commit
above backported, it would take care of this issue for most users.
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu)
Status: New => Confirmed
--
You
Uploading a LXD SRU to bionic with the one commit cherry-picked shouldn't be
too hard.
But we'd need someone to sort out the SRU paperwork as I have no idea how we'd
even test the fix.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
Just tested this update with a running container and the upgrade went through
correctly.
It's hard to tell if this would have normally failed given that based on the
output, shmounts and devlxd weren't mounted at the time things got purged but
it at least shows that the potentially problematic
Just tested this by running the new package on an Ubuntu 18.04 system
with LXD 3.0 running (including one running instance).
The prompt showed up as expected and indeed just offered 3.0 and 4.0 with 4.0
selected as default.
Upgrade worked and container is still functional on the 4.0 snap.
**
The warning message:
"""
Warning from stdin (line 1): apparmor_parser: Warning capping number of jobs to
0 * # of cpus == '16'
"""
Is caused by a LXCFS bug which we've since fixed. Systems still showing
this message are in need of a snap refresh and host reboot.
It's quite likely that the
** Patch added: "lxcfs_5.0.0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1965427/+attachment/5570157/+files/lxcfs_5.0.0.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
LXCFS 5.0 LTS was released last week.
The highlights of this is:
- Switch to meson build system
- Better detection and handling of CGroup2
- /proc/slabinfo support
- /sys/devices/system/cpu support
Of those, only the last two are user visible changes and just result in
** Description changed:
running do-release-upgrade from ubuntu 18.04 to 20.04 i got this upgrade
error for lxd
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lxd 3.0.3-0ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux
lxd_0.10_source.changes uploaded to the queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964833
Title:
Disable "latest" as upgrade option on focal
To manage notifications about this bug go to:
Note that I'm not pushing for an impish version of this change as this
package in impish is unused.
The transitional "lxd" package is only relevant when upgrading from a
pre-snap system which is only possible when upgrading from bionic to
focal. The package has now been removed entirely from
Public bug reported:
The "lxd" transitional deb-to-snap package currently offers "3.0", "4.0"
and "latest" as track options with "4.0" being the recommended and
default one.
Starting with LXD 5.0, it will no longer be possible to upgrade from LXD
3.0 without first going through LXD 4.0. As a
Removing packages from jammy:
lxd 1:0.9 in jammy
lxd 1:0.9 in jammy amd64
lxd 1:0.9 in jammy arm64
lxd 1:0.9 in jammy armhf
lxd 1:0.9 in jammy i386
lxd 1:0.9 in jammy ppc64el
lxd 1:0.9 in jammy
Basically `adapt` expects that `images.linuxcontainers.org` is a LXD-
protocol server, it doesn't know about our transition to simplestreams
starting at around LXD 2.0.4 (August 2016) and those image servers have
not actually supported that older API for a long time now.
** Changed in: adapt
The `adapt` package has been broken since at least 2016 as it hardcodes
an image server path and patterns that haven't been valid for years.
As a result, it's impossible for anyone to have successfully used adapt
on Ubuntu since pre-16.04.
--
You received this bug notification because you are a
Public bug reported:
The `lxd` package (`lxd`, `lxd-client`, `lxd-tools`) has been replaced
by a snap starting with Ubuntu 18.10. To facilitate that, the main `lxd`
package was turned into an automatic conversion package which on install
will trigger the installation of the snap and migration of
This bug was fixed in the package lttng-modules - 2.13.1-1
Sponsored for Michael Jeanson (mjeanson)
---
lttng-modules (2.13.1-1) unstable; urgency=medium
* [a4701a4] New upstream version 2.13.1
-- Michael Jeanson Wed, 05 Jan 2022 14:08:28
-0500
lttng-modules (2.13.0-2)
Approving this FFe with my ubuntu-release hat on, the new features are
fine especially as the userspace side is already present and the fact
that things aren't lined up currently is a bit of an issue.
** Summary changed:
- lttng-modules is out of sync with lttng-tools
+ [FFE] lttng-modules is
@jjohansen nope, we use the apparmor_parser that ships in core20.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964636
Title:
Incorrect handling of apparmor `bpf` capability
To manage
Yeah, that's because you're using LXD 4.23 which has the older LXCFS and
doesn't trigger the apparmor warning message which then confuses
everything else (per previous comment).
If you `snap install lxd --channel=latest/edge`, you should start getting the
broken behavior.
Note however that we
As part of digging into this issue, I found this error:
```
Warning from stdin (line 1): apparmor_parser: Warning capping number of jobs to
0 * # of cpus == '4'
```
Which started appearing since we released LXCFS 5.0.0 (available in LXD edge
and candidate).
The root cause is
The steps in the description reproduce this issue for me on a clean
Ubuntu 20.04 server install on either 5.4.0 (GA) or 5.13.0 (HWE)
kernels.
The container doesn't need to be privileged. The main steps really seem
to be the installation of a classic snap followed by restart of the
container.
--
Public bug reported:
We've recently noticed a lot of the LXD CI jobs failing because of
apparmor related snapd issues.
The way this usually manifests is:
- lxc launch images:ubuntu/20.04 c1
- lxc exec c1 -- apt install snapd
- lxc exec c1 -- snap install distrobuilder --edge --classic
- lxc
Uploaded the exact same thing to impish queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959993
Title:
SRU of LXC 4.0.12 to focal (upstream bugfix release)
To manage notifications about this
Thanks Brian, my memory of this whole thing clearly dates back a long
time then ;)
I still remember some of the discussions of what we'd expect people to
be doing in such cases and whether we'd ever officially support (as in
test/validate) upgrade paths other than release to release+1 and LTS to
Marking this invalid against LXC as the code in the archive for package
testing is handling this case properly already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960847
Title:
lxc autopkgtests
The autopkgtest script in the Ubuntu package has:
# Skip some tests due to cgroup v2 incompatibility
if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then
[ "$testbin" = "lxc-test-apparmor-mount" ] && \
ignore "$STRING" && continue
[ "$testbin" =
(We technically had the same issue with the previous upload as 4.0.6 was
higher than what hirsute shipped at the time, though in that case the
EOL for hirsute was just a month or so away making the case for skipping
that SRU even stronger :))
--
You received this bug notification because you are
In general, it's indeed a problem for such cases, though there are a few
mitigating factors here:
- This would only be a problem for those who upgrade from focal to
impish. My understanding is that there is no direct upgrade path to
achieve this, you'd need to go throughgroovy and hirsute, both
Closing the LXC task for now as that seems to be unrelated to a LXC
change (we haven't uploaded in a while) and not related to a new kernel
release which could actually cause such a change.
If you track this down to something other than an issue in your test
environment, please add lxc to this
** Changed in: lxc (Ubuntu)
Status: Incomplete => Invalid
** Changed in: lxc (Ubuntu Focal)
Status: Incomplete => Invalid
** No longer affects: lxc (Ubuntu)
** No longer affects: lxc (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I think the strlcat thing is a red herring or an indication that the
test environment is somehow in a bad shape. This could be explained if
there was two versions of liblxc on the system for example.
Outside of that, I'm also seeing:
```
lxc-start tmp.KEpxw2rh0e 20220205081512.354 ERROR
Hmm, hold on, this makes no sense.
You're reporting this against focal, but 4.0.12-0ubuntu1 is the jammy
version of lxc, so what's going on here exactly?
Also, all the links posted are unreachable, please avoid internal links
and attach the logs instead.
** Changed in: lxc (Ubuntu)
Worth noting that with this upload, the packaging gets virtually in sync
with jammy minus a few artifacts of git-dpm in the patches, this should
make maintenance a fair bit easier should a follow-up SRU be needed.
Upstream packaging delta:
Source package and all resulting binary packages are "lintian -iI" clean
except for the warning caused by SRU version numbering.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959993
Title:
SRU of
Uploaded to focal SRU queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959993
Title:
SRU of LXC 4.0.12 to focal (upstream bugfix release)
To manage notifications about this bug go to:
A build of the proposed SRU is available for all architectures (well,
riscv64 is slowly building) at:
https://launchpad.net/~stgraber/+archive/ubuntu/experimental-devirt/
** Description changed:
- LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like to
line things up in focal.
are
functional.
** Affects: lxc (Ubuntu)
Importance: Undecided
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You re
** Changed in: lxc (Ubuntu)
Status: Triaged => 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/1502604
Title:
autopkgtests fail in LXC testbed
To manage notifications about this bug
Closing as these days we only have LXD preinstalled on those images and
LXD does a lot more validation and only creates the networks on first
use.
** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: lxc (Ubuntu)
Status: Triaged => 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/1591124
Title:
LXC: Cannot create a container with the specific alias "tasks"
To
Closing the LXC side of this bug as there's nothing we can really do here.
It's either a kernel issue (needs support for their socket option within a
network namespace) or an open-iscsi issue where they could have some kind of
fallback mechanism.
** Changed in: lxc (Ubuntu)
Status:
** Changed in: lxc (Ubuntu)
Status: Triaged => 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/1522992
Title:
/usr/bin/lxc-
Ubuntu Touch hasn't been a thing for a few years and UBPorts hasn't
really been hitting this issue as far as I know.
** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@brauner do you know what's the state of quotas in a VFS idmapped
shifted world?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515615
Title:
Disk quotas don't work in LXC containers
To manage
Closing as it's not really LXC's job to try and change that one.
These days we'd recommend distros to change default permissions or
ideally get that changed at the kernel level. Short of that, we do have
some documented recommendations in our production environment doc for
LXD:
Moving over to the kernel as a userspace process shouldn't be able to
cause such a hang regardless of what it does so this looks like a kernel
bug (lock related by the looks of it).
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member
** Changed in: lxc (Ubuntu)
Status: Confirmed => 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/1646462
Title:
lxc-create cannot setgid
To manage notifications about this bug go
Could you recheck with the current LXC (4.0.12) as the cgroup code was
reworked quite extensively.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
CRIU is once again in the archive (Ubuntu is just following what's in
Debian for this one).
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did we ever see this one again or was it just transient?
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881292
Title:
Linux 5.7:
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883041
Title:
libpam-cgfs fails to create freezer cgroup writable by user
To manage
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Released
** Changed in: lxc (Ubuntu Bionic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886790
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887919
Title:
autopkgtest failure with libselinux 3.1
To manage notifications about this
Are we still seeing this?
The failure looks a lot like it could be a legitimate kernel issue.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
** Changed in: lxc (Ubuntu Focal)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Said change is in LXCFS 4.0.12 which is now in jammy
** Changed in: lxcfs (Ubuntu)
Status: Triaged => 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/1947811
Title:
cgroups
** Changed in: lxc (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: libnih (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1532314
Seems green lately
** Changed in: lxc (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/1916669
Title:
autopkgtests flaky for hirsute across various
The error you're getting is coming from systemd in the container which
for some reason is trying to mount a cgroup1 hierarchy rather than using
cgroup2 like the rest of your system.
You may be able to workaround that by using `lxc.init_cmd` to pass
/sbin/init with additional arguments to change
** Changed in: lxc (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/1917601
Title:
lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
To
Marking as invalid as this wasn't an LXC bug but a kernel bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931064
Title:
lxc autotest failure with kernel >= 5.13
To manage notifications about
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=591a22c14d3f45cc38bd1931c593c221df2f1881
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lxc (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957934
Title:
error in man page for lxc.container.conf
To manage notifications about
Closing the LXD task as there's not really anything we can do there.
The options here are pretty much:
- Do nothing, if it's just privileged containers, it's usually not a big deal
- Significantly rework apparmor mount handling logic and policies so this can
be safely allowed
- Ship unit
If this only fails in privileged containers, then I probably wouldn't
worry about it too much, those aren't the default and a LOT of things
break in privileged containers, so I don't think it's worth doing distro
changes to accommodate this, assuming the container otherwise still
boots.
For cases
Privileged containers have a much stricter apparmor policy applied than
unprivileged containers.
That's because unprivileged containers primarily rely on the user namespace to
prevent breakout and taking over of the host whereas privileged containers rely
entirely on apparmor.
As apparmor
** Package changed: lxd (Ubuntu) => linux-raspi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948573
Title:
Failure to start container “Failed to start device “eth0”: Error:
Unknown
*** This bug is a duplicate of bug 1712808 ***
https://bugs.launchpad.net/bugs/1712808
** This bug has been marked a duplicate of bug 1712808
udev interface fails in privileged containers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** No longer affects: lxd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873004
Title:
lxd interaction blocked until snapd was restarted
To manage notifications about this bug go to:
- Setup snap "snapd" (9721) security profiles (cannot reload udev rules:
exit status 1
Was that when updating a privileged LXD container by any chance?
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I suspect you probably found a way out of this by now but if not or if
you're hitting this on another system, let me know and I'll sort
something out.
It would have been interesting to see what those symlinks are pointing
to, they may not have been rewritten properly due to the failure partway
** Package changed: lxd (Ubuntu) => snapd (Ubuntu)
** Summary changed:
- package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package
pre-installation script subprocess returned error exit status 1
+ snapd failure when /home is a symlink
--
You received this bug notification
- Run install hook of "lxd" snap if present (run hook "install":
/var/lib/snapd not root-owned 0:110)
That's a new one I've never seen before. This suggests that directory
ownership for /var/lib/snapd is quite wrong on your system which in turn
causes some snapd actions to fail.
I'll re-assign
- Download snap "snapd" (10492) from channel "stable" (Get
https://canonical-bos01.cdn.snapcraft.io/download-origin/canonical-
lgw01/PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4_10492.snap?interactive=1=1609376400_22d9f1ee728894ebbb147d6cf985e1b06e1fbccd:
dial tcp 91.189.91.42:443: connect: connection timed
error: unable to contact snap store
This shows the reason for the failure, it's likely the system having
dropped offline at the time or some other kind of networking or
firewalling issues preventing your system from reaching the package
store.
** Changed in: lxd (Ubuntu)
Status: New =>
That's pretty confusing, it shows as if it crashed while trying to test
connectivity with the snap store but this appears to be outside of our
script and is weirdly mixed in with gnome session output.
Did you manage to fully unstick that system and apply all remaining
updates afterwards?
**
error: Unable to connect to the source LXD: Get
"http://unix.socket/1.0": dial unix /var/lib/lxd/unix.socket: connect:
connection refused
This actually suggests a LXD upgrade failure. If this can be reproduce,
the output of `journalctl -u snap.lxd.daemon -n 300` would be quite
useful.
** Changed
The issue with this one is translation handling in the old version of LXD.
The migration script has since been changed to force LANG=C.UTF-8 to avoid such
issues.
** Changed in: lxd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
- Setup snap "core" (10577) security profiles (cannot setup udev for
snap "core": cannot reload udev rules: exit status 1
Is that an update running inside of a privileged LXD container by any
chance?
** Changed in: lxd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
** Changed in: lxd (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/1923685
Title:
Unable to deploy LXD VM host on S390X
To manage notifications about this
error: unable to contact snap store
This suggests the system had network connectivity issues at the time of the
upgrade.
Did re-trying the upgrade get you through to the end eventually?
Assuming this is all inside of a container (as your systemd change
suggests), an alternative is to just
- Setup snap "snapd" (12057) security profiles (cannot reload udev
rules: exit status 1
Is this an upgrade running inside of a privileged lxd container by any
chance?
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
error: system does not fully support snapd: cannot mount squashfs image using
"squashfs": mount:
/tmp/sanity-mountpoint-913738666: mount failed: Operation not permitted.
This looks odd, snapd should know to use snapfuse in such environments.
Can you show "lxc config show --expanded" of
1 - 100 of 7691 matches
Mail list logo
