* Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Trusty)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubu
signee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxd (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxd (Ubuntu Cosmic)
Importance: Undecided => Low
** Changed in: lxd (Ubuntu)
Status: Triaged => Fix Committed
--
You
It feels like a lot of this pain comes from the fact that we are pushing
an Ubuntu Cloud image to those users when large parts of that image are
not going to be functional due to lack of systemd or some kernel APIs.
A better option would be to strip the WSL image down to a set of package that's
Yeah, so that's going to be a bit of an issue for some users as without
snapd working in this environment, they'll actually loose the lxd client
as part of the upgrade.
Whether that's an actual issue when the lxd client works natively on
Windows, I don't really know.
--
You received this bug
Yeah, unprivileged LXC is likely to work pretty differently in the way
it handles both cgroups and apparmor namespacing both of which are very
relevant when you want to run snaps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This shows a network issue during upgrade, failing to reach api.snapcraft.io
apparently.
There is a good chance that a re-try sorted this one, if not, then there's
something odd going on with networking.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug
*** This bug is a duplicate of bug 1821924 ***
https://bugs.launchpad.net/bugs/1821924
** Changed in: lxd (Ubuntu)
Status: New => Invalid
** This bug has been marked a duplicate of bug 1821924
LXD Deb->snap transition fails in WSL due to snap command not working (yet)
--
You
** Changed in: lxd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813622
Title:
systemd-resolved, systemd-networkd and others fail to start in lxc
*** This bug is a duplicate of bug 1821924 ***
https://bugs.launchpad.net/bugs/1821924
** This bug has been marked a duplicate of bug 1821924
LXD Deb->snap transition fails in WSL due to snap command not working (yet)
--
You received this bug notification because you are a member of
Fehler: cannot add authorization: open /home/yannick/.snap/auth.json:
input/output error
This suggests some storage issue, potentially bad drive causing the upgrade to
fail.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
Moving over to snapd as the failure actually hits before any of the LXD
migration code runs.
This shows a failure in setting up the environment for the configure
hook, likely related to snapd passing /var/lib/lxd into the mount
namespace. I don't know if this is still a thing that it does, but if
Closing the LXD side of this (tasks would likely have been better) as
there's indeed nothing particularly special that LXD does here and
usually the right approach is to track down what the package in question
is doing and fix it there.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
** Changed in: lxd (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/1665943
Title:
Home directory has wrong ownership if created by lxd in arranging a
mount
Re-opened as low as in the case where LXD is unused, we could indeed
skip the migration and just complain loudly about not being able to
install the snap.
The definition of "unused" here would be whether LXD was ever activated
since only the migration tool can properly analyse the database to
Hmm, cgroup:rw has absolutely nothing to do with this.
LXD uses a cgroup namespace by default which completely ignores that particular
setting.
With the cgroup namespace, root in the container is allowed to do
anything it wants to the /sys/fs/cgroup tree.
root@disco:~# mkdir
We still wouldn't be using the lxd-installer, instead the built-in
command wrappers for lxc and lxd should just be made to fail with an
error indicating that LXD should be manually installed.
Automatic installation on first use is something that's unlikely to be
very supportable as it wouldn't
I don't believe that dist-upgrading WSL is officially supported as it's
an Ubuntu installation which does not run a supported Ubuntu kernel. As
you point out, LXD cannot work in such an environment and so it's
reasonable for its upgrade to similarly fail.
The lxd-installer proposal also isn't
This is causing MAAS deployments using trusty + hwe-x to silently end up
with the wrong kernel.
** Changed in: linux-meta-lts-xenial (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The upstream announcement is now available here:
https://discuss.linuxcontainers.org/t/lxc-2-0-11-has-been-released/4238
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816642
Title:
SRU of LXC
Uploaded to the SRU queue for Ubuntu 16.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816642
Title:
SRU of LXC 2.0.11
To manage notifications about this bug go to:
** Summary changed:
- SRU of LXC 2.0.10
+ SRU of LXC 2.0.11
** Description changed:
LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the
changelog for both of them can be found below:
+ LXC
We'll have to make that 2.0.11 as unfortunately the 2.0.10 release
tarball is bad, waiting for the new release to unblock this bug.
** Changed in: lxc (Ubuntu Trusty)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Xenial)
Assignee: (unassig
Public bug reported:
LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog
for both of them can be found below:
LXC 2.0.10:
- tools: allow lxc-attach to undefined containers
- utils: move
Yeah, not much LXD can do about this unfortunately. We do create any
missing intermediate directories as can be seen in this case, but
there's no good way to know what the owner of every one of those
intermediate directories should be, nor would it help here as skel still
wouldn't get applied.
*** This bug is a duplicate of bug 1641236 ***
https://bugs.launchpad.net/bugs/1641236
** This bug has been marked a duplicate of bug 1641236
Confined processes inside container cannot fully access host pty device
passed in by lxc exec
--
You received this bug notification because you
The log submitted as part of this issue indicates that the snap store
couldn't be reached during the upgrade. It shows that you selected to
abort the upgrade when prompted about snap store connectivity.
The message displayed did include:
```
Aborting will cause the upgrade to fail and will
This is a LXD commit, not a LXC one. LXC cannot be fixed in the same way
as it has a single apparmor policy covering both privileged and
unprivileged containers, until such time as the apparmor security issue
is resolved, there's nothing we can do to fix this issue without causing
a giant security
** Changed in: lxd (Ubuntu Xenial)
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/1804876
Title:
SRU of LXD 3.0.3
To manage notifications about this bug go
** Changed in: lxc (Ubuntu Xenial)
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/1804755
Title:
SRU of LXC 3.0.3 (upstream bugfix release)
To manage
** Changed in: lxcfs (Ubuntu Xenial)
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/1804753
Title:
SRU of LXCFS 3.0.3 (upstream bugfix release)
To manage
The verification of the Stable Release Update for lxd has completed
successfully and the package has now been 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
Tested the upgrade on a running system, containers weren't restarted as
part of the upgrade (expected), new containers after upgrade worked
properly and containers worked as expected post-reboot.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
The verification of the Stable Release Update for lxcfs has completed
successfully and the package has now been 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
Updated a bionic and cosmic system, containers kept working fine, newly
started ones are good too.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You received this
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been 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
Tested the bionic and cosmic SRUs with LXD and LXC containers, upgrade
doesn't break containers and newly containers are fine too.
Limits render as expected.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
Trace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fe70ae4e3b2 in cg_readdir (path=, buf=0x7fe690003610,
filler=0x7fe70b850ce0 , offset=, fi=)
at bindings.c:1793
1793bindings.c: No such file or directory.
[Current thread is 1 (Thread 0x7fe708850700 (LWP 3871))]
We never had any other report of this so it's not a generic issue in
libpam-cgfs, this suggests a debconf issue, so closing the lxcfs task.
** Changed in: lxcfs (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Closing as Invalid as there's no good way around this issue in general.
The kernel will let you mount controllers that were already mounted but
will complain if options don't perfectly match. Those options may differ
for a number of reason and making lxcfs match those from systemd just
means,
Well, the adt setup in this case just can't work, you can't tell apt to
install lxc-utils from -updates and liblxc1 from -proposed when they
have strict dependencies between them, you're just going to be getting
an apt failure.
--
You received this bug notification because you are a member of
This system is using a mix of -proposed and non-proposed packages, this
isn't going to work and isn't supported, marking invalid.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: lxd (Ubuntu Xenial)
Importance: Medium => High
** Changed in: lxd (Ubuntu Bionic)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804876
Title:
SRU
Uploaded to bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804876
Title:
SRU of LXD 3.0.3
To manage notifications about this bug go to:
same version everywhere.
** Affects: lxd (Ubuntu)
Importance: Medium
Assignee: Stéphane Graber (stgraber)
Status: Invalid
** Affects: lxd (Ubuntu Xenial)
Importance: Medium
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Affects: lxd (Ubuntu Bionic)
** Changed in: lxd (Ubuntu Xenial)
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/1788280
Title:
SRU of LXD 3.0.2
To manage notifications about this bug go
And the bionic version too
** Changed in: lxc (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: lxc (Ubuntu Cosmic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Uploaded to cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804755
Title:
SRU of LXC 3.0.3 (upstream bugfix release)
To manage notifications about this bug go to:
Uploaded to disco, will wait for autopkgtest to be happy before I start
pushing the SRUs.
** Changed in: lxc (Ubuntu Xenial)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Bionic)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed i
Public bug reported:
LXC upstream released LXC 3.0.3 as a bugfix release with following
changelog:
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style
** Changed in: lxc (Ubuntu Xenial)
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/1788457
Title:
SRU of LXC 3.0.2 (upstream bugfix release)
To manage
Uploaded to disco, cosmic and bionic.
Xenial will wait until we're in bionic-updates.
** Changed in: lxcfs (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: lxcfs (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a
: Stéphane Graber (stgraber)
Status: In Progress
** Affects: lxcfs (Ubuntu Xenial)
Importance: Medium
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Affects: lxcfs (Ubuntu Bionic)
Importance: Medium
Assignee: Stéphane Graber (stgraber)
Status
** Changed in: lxcfs (Ubuntu Xenial)
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/1788232
Title:
SRU of LXCFS 3.0.2 (upstream bugfix release)
To manage
Yes, according to that URL, 3.0.2-0ubuntu1~18.04.1 is green as of
2018-11-09 14:17:52 UTC
** Changed in: lxd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Current result for 18.04 arm64 is a success, closing.
** Changed in: lxd (Ubuntu)
Status: Confirmed => Invalid
** No longer affects: lxd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803344
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => 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/1789746
Title:
getxattr: always handle namespaced attributes
To
** 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/1800442
Title:
lxd deb to snap preinst fails: "rm: skipping '/var/lib/lxd/storage-
It's kinda hard to tell what's going on because of all that systemd mess.
It looks to me like there was somehow a leftover process from LXD 3.0.1 that'd
keep the database open and prevent the 3.0.2 version from properly starting up
and applying the update but without a system to poke at, it's
Fix merged upstream and cherry-picked to the snap, expect rollout within
24h
** Changed in: lxd (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Found the culprit, will still have to track down exactly why that is and
how to fix it, but with LXD tasks disabled internally, I'm seeing:
original: 520 context switches per second
modified: 26 context switches per second
original: 150mW of estimated power consumption
modified: 130uW of
Hmm, unfortunately the initial run would have been different I suspect.
It looks like the cleanup partly run once and now it's just getting stuck on
some leftover mounts.
I suspect we won't be getting to the bottom of what happened here
anymore, but we should at least be able to clean things up,
Ok, so the issue here is:
- error: The source server is part of a LXD cluster, this isn't
supported.
Which kinda says it all as migrating from a non-snap to a snapped LXD
cluster is particularly tricky and something we weren't confident we
could achieve automatically in a reliable way.
That
Mark as invalid for LXD as there's unfortunately nothing we can do in
our packaging to detect this case and work around it without having to
cause an upgrade failure which the user then has to retry.
Our script runs a connectivity check with the store, unfortunately that
connectivity check
The entire output of "journalctl -u lxd" would be useful as would
/var/log/lxd/lxd.log (and any older version of that file available in
the directory).
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The Linux implementation of WSL doesn't allow for LXD to run at this
time.
** Changed in: lxd (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/1801581
Title:
Marking the LXD side of this fixed as we're now shipping as a snap by
default and the snap contains zfs.
** Changed in: lxd (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did an upgrade test from 3.0.1 with running containers, upgrade worked
fine, post-reboot system is fine, launching containers works fine.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug
The verification of the Stable Release Update for lxd has completed
successfully and the package has now been 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 has now been 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
Oh, I am also using zram-config on the affected machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799497
Title:
4.15 kernel hard lockup about once a week
To manage notifications about this
Just happened again, though the machine wouldn't reboot at all
afterwards, leading to the hosting provider going for a motherboard
replacement, so I guess better luck next week with debugging this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Oh, unless budgie is using some different tool for the update, I'm not
too sure about that part, if so, it'd probably explain why we didn't get
much more report of this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, re-targeting to update-manager as it sounds like what was used here.
** Package changed: lxd (Ubuntu) => update-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799973
Title:
Yeah, we've seen that re-running the command usually gets you past the
error, so in your case, just running the "snap install go --classic"
would likely have been enough.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
How did you start the 18.04 to 18.10 upgrade?
The LXD deb uses standard debconf interactions to show those dialogs, so
the same would apply to any package that requires prompting during the
upgrade.
Your symptoms could be explained by a script or tool wrapping the
upgrader, effectively messing
The server doesn't respond to pings when locked up.
I do have IPMI and console redirection going for my server and have
enabled all sysrq now though it's unclear whether I can send those
through the BMC yet (as just typing them would obviously send them to my
laptop...).
I've setup debug console
Note that I've deleted the wifisyslog and currentdmesg as they're not
relevant (current boot) and included information that I'd rather not
have exposed publicly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1799497/+attachment/5204637/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799497
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1799497/+attachment/5204634/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799497
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1799497/+attachment/5204635/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1799497/+attachment/5204636/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1799497/+attachment/5204639/+files/WifiSyslog.txt
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799497/+attachment/5204633/+files/CurrentDmesg.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1799497/+attachment/5204638/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799497
Title:
Oh and whatever kernel I boot needs to have support for ZFS 0.7 or I
won't be able to read my drives.
** Tags added: apport-collected
** Description changed:
My main server has been running into hard lockups about once a week ever
since I switched to the 4.15 Ubuntu 18.04 kernel.
When
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1799497/+attachment/5204633/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, kinda, this is a production server running a lot of publicly
visible services, so I can run test kernels on it so long as they don't
regress system security.
There's also the unfortunate problem that it takes over a week for me to
see the problem in most cases and that my last known good
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1799497/+attachment/5204632/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799497
Title:
4.15
Public bug reported:
My main server has been running into hard lockups about once a week ever
since I switched to the 4.15 Ubuntu 18.04 kernel.
When this happens, nothing is printed to the console, it's effectively
stuck showing a login prompt. The system is running with panic=1 on the
cmdline
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been 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
I've confirmed the the update happens smoothly, that existing containers
can be interacted with just fine and that newly started containers work
too.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this
Tested on bionic, upgrading reloaded lxcfs without impacting running
containers and everything still works after a reboot too.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because
The verification of the Stable Release Update for lxcfs has completed
successfully and the package has now been 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 stable snap now contains this code.
** Changed in: lxd (Ubuntu)
Status: Fix Committed => 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/1797440
Title:
lxd is too restrictive
** Changed in: lxd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797440
Title:
lxd is too restrictive about ciphers when it comes to proxies
Subscribed the LXD team directly as we are obviously interested in this
issue.
Then moved the bug from lxd over to snapd since as far as LXD's
concerned, we've fixed the bug on our side (activate hanging for 10s),
with this fixed, LXD spends less than a second on boot to check whether
it's
A number more timeouts are now set in recent LXDs and I've not run into
such a situation ever since, so I think we're good to close this.
** Changed in: lxd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, so most proxies do not intercept TLS and instead let you send
"CONNECT" through and connect to the target server, in which case
there's no reason for us to compromise on ciphers and allow for a
potential downgrade and breaking of PFS.
Since we can't really detect a company proxy which does
I've heard that even cloud images that were shipping snaps before the
LXD inclusion are seeing a ~10s slowdown. If that's indeed the case, can
we get a before/after for those with:
- systemd-analyze critical-chain
- journalctl --boot 0
- ps fauxww
The LXD snap at boot time should be spending
snapd has now migrated to the release pocket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796137
Title:
huge and slow image 20181002 due to seeded lxd snap
To manage notifications about this bug
The updated LXD snap should be available now in the stable channel.
The updated snapd is in cosmic-proposed and will hopefully migrate over the
weekend.
Assuming that does happen, it'd be good to re-check cloud image on
Monday.
--
You received this bug notification because you are a member of
401 - 500 of 7691 matches
Mail list logo
