This should be fixed in the latest release. It has not been SRUd.
** Changed in: lxcfs (Ubuntu)
Status: Fix Committed => Fix Released
** Also affects: lxcfs (Ubuntu Wily)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Hm, a second run did not reproduce the error. If I can't get it to
happen again in a few hours of re-trying, I'll assume it was a fluke or
related to the host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hm, a second run did not reproduce the error. If I can't get it to
happen again in a few hours of re-trying, I'll assume it was a fluke or
related to the host.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Description changed:
+
+ SRU Justification
+ Impact: xenial containers cannot be rebooted
+ Fix: shorten the fuse directory entry caching time, and make lxc (when using
lxcfs) wait at least that amount of time during reboot.
+ Test case:
+ lxc-create
I could not reproduce the original issue, but the new qemu packages
appear to be regression-free, so marked this verification-done on that
grounds. If the SRU team prefers to kick this package I'm ok with that
as well.
** Tags removed: verification-needed
** Tags added: verification-done
--
I could not reproduce the original issue, but the new qemu packages
appear to be regression-free, so marked this verification-done on that
grounds. If the SRU team prefers to kick this package I'm ok with that
as well.
** Tags removed: verification-needed
** Tags added: verification-done
--
Could you please give the full command you used so that I can reproduce
this?
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516203
Could you please give the full command you used so that I can reproduce
this?
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
@jpvr,
The patch for virt-aa-helper to handle the nvram files is upstream, and
should hit xenial with the next merge. Then you shouldn't need the
template workaround.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a
Thanks. (I thought I had upgraded my test system to xenial, but I
hadn't, so virtio-vga was not supported)
How far into the boot do you see this happening?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Thanks. (I thought I had upgraded my test system to xenial, but I
hadn't, so virtio-vga was not supported)
How far into the boot do you see this happening?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah, interesting. So this may be a bug in aa-complain, as it did not
retain (iiuc) the attach_disconnected flags.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
Ah, interesting. So this may be a bug in aa-complain, as it did not
retain (iiuc) the attach_disconnected flags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
lxc-start fails with
(Note I cannot reproduce this here)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1516203
Title:
qemu-system-x86_64 crashed with SIGSEGV in SDL_BlitCopy()
To manage notifications
(Note I cannot reproduce this here)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516203
Title:
qemu-system-x86_64 crashed with SIGSEGV in SDL_BlitCopy()
To manage notifications about this bug go
** Changed in: libvirt (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1398999
Title:
Block migrate with attac
** Changed in: libvirt (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398999
Title:
Block migrate with attached volumes cop
What do you mean by "not using real device"? The real lvm device is
mounted into the container. However actually offering the device node
into the container would not be a safe default. In particular, it
allows the container admin to write nonsense onto the device node,
feeding garbage into the
Could you post the container configuration file?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
To manage notifications about this
Could you post the container configuration file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
To manage notifications about this bug go to:
How about a comment in the /etc/default/lxc-net file?
I guess the question is - when it broke for you, which files did you
first look at to try to fix it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Once Seth's work enabling mounting inside containers is complete, we'll
most likely want some way of enabling quotas, so leaving this open as a
wishlist (feature request/enhancement) item.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Nm, afaict yama should never prevent this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
To manage notifications about this bug go
Nm, afaict yama should never prevent this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
To manage notifications about this bug go to:
What does
ls -l /proc/sys/kernel/yama/
cat /proc/sys/kernel/yama/ptrace_scope
show?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
@faux
do you still have this issue?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1452601
Title:
vivid container's networking.service fails on boot with signal=PIPE
To manage
@faux
do you still have this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452601
Title:
vivid container's networking.service fails on boot with signal=PIPE
To manage notifications about
What do you mean by "not using real device"? The real lvm device is
mounted into the container. However actually offering the device node
into the container would not be a safe default. In particular, it
allows the container admin to write nonsense onto the device node,
feeding garbage into the
Once Seth's work enabling mounting inside containers is complete, we'll
most likely want some way of enabling quotas, so leaving this open as a
wishlist (feature request/enhancement) item.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
What does
ls -l /proc/sys/kernel/yama/
cat /proc/sys/kernel/yama/ptrace_scope
show?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
To manage
How about a comment in the /etc/default/lxc-net file?
I guess the question is - when it broke for you, which files did you
first look at to try to fix it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for reporting this bug.
Can you tell use exactly how you told virt-manager about the printer?
For other types of usb devices (like an ereader) this has definately
created the needed rules for me.
Adding a blanket '/run/udev/** rw' rule would not be safe, but we should
be able to find a
Thanks - could you show the vm's xml configuration? (i.e. result of
virsh dumpxml vmname)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515791
Title:
apparmor for qemu is too restrictive for USB
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1514690
Title:
rebooting container with systemd >= 226 fails to
Hi Chuck,
could you request whatever openstack config info we'd need to reproduce
this?
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Chuck Short (zulcss)
--
You received this bug notification because you are a
** Changed in: lxc (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/1514690
Title:
rebooting container with systemd >= 226 fails to create
What is the lxc.rootfs option? Does it point to an xfs backed device?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1515615
Title:
Disk quotas don't work in LXC containers
To manage
What is the lxc.rootfs option? Does it point to an xfs backed device?
--
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 notifications
Ok, I asked because according to mount(2) that option appears to be
ignored except for xfs filesystems.
If you look at /proc/self/mountinfo you'll see that usrquota is in fact
in the list of mount options, so lxc is respecting that.
At the moment your problem is that the device backing your
Ok, I asked because according to mount(2) that option appears to be
ignored except for xfs filesystems.
If you look at /proc/self/mountinfo you'll see that usrquota is in fact
in the list of mount options, so lxc is respecting that.
At the moment your problem is that the device backing your
Actually that might not help. If the cgroup really did still exist,
then lxc would have refused to re-use it. I.e .instead of /lxc/x1, it
would then use /lxc/x1-1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yup, just making lxc sleep 2 seconds works. So this is purely a race.
I'll fix it by having lxc excplicitly wait until the cgroups are removed
before re-execing after reboot.
** Changed in: lxc (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you
Yup, just making lxc sleep 2 seconds works. So this is purely a race.
I'll fix it by having lxc excplicitly wait until the cgroups are removed
before re-execing after reboot.
** Changed in: lxc (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you
Actually that might not help. If the cgroup really did still exist,
then lxc would have refused to re-use it. I.e .instead of /lxc/x1, it
would then use /lxc/x1-1.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
So the problem is indeed that the cgroups are deleted using the
cgroupfs, and fuse doesn't get that information. The fuse kernel module
is caching the information for one second before re-querying userspace.
I've pushed a patch to lxcfs to drop the caching to a half second. I'm
posting a patch
So the problem is indeed that the cgroups are deleted using the
cgroupfs, and fuse doesn't get that information. The fuse kernel module
is caching the information for one second before re-querying userspace.
I've pushed a patch to lxcfs to drop the caching to a half second. I'm
posting a patch
@oleg,
yes, but it is not an lxc bug, there's nothing lxc can do about it.
Stéphane un-marked it from lxc to make the lxc bug view more usable so
we can use it rather than ignore it :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@oleg,
yes, but it is not an lxc bug, there's nothing lxc can do about it.
Stéphane un-marked it from lxc to make the lxc bug view more usable so
we can use it rather than ignore it :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The download template (which is recommended) installs no ssh and no
ubuntu password.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514080
Title:
lxc-templates lacks template for ubuntu core
To
The download template (which is recommended) installs no ssh and no
ubuntu password.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1514080
Title:
lxc-templates lacks template for
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchp
That was a red herring, actually. The cause of failure appears to be
the next line.
After fixing that so that the mkdir succeeds, it still fails on
Failed to allocate manager object: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
That was a red herring, actually. The cause of failure appears to be
the next line.
After fixing that so that the mkdir succeeds, it still fails on
Failed to allocate manager object: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
With cgfs i actually wasn't able to start the container in the first
place. I've now fixed at least that.
it wasn't the mkdir which was failing, but the subsequent attempt to
attach itself to it. That's because while cgmanager used to chown the
child files after creating a directory for us,
With cgfs i actually wasn't able to start the container in the first
place. I've now fixed at least that.
it wasn't the mkdir which was failing, but the subsequent attempt to
attach itself to it. That's because while cgmanager used to chown the
child files after creating a directory for us,
When I test this using cgfs-backed lxcfs, the mkdir of init.cgroup fails after
setresuid(10, 10, 0).
This is odd since doing it manually using sudo -u \#10 -g \#10 mkdir
/sys/fs/cgroup/systemd/lxc/x1/x works fine.
--
You received this bug notification because you are a member
Doh', it's because I had a total brainfart while writing that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514690
Title:
rebooting container with systemd >= 226 fails to create /lxc/adt-
Doh', it's because I had a total brainfart while writing that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1514690
Title:
rebooting container with systemd >= 226 fails to create
When I test this using cgfs-backed lxcfs, the mkdir of init.cgroup fails after
setresuid(10, 10, 0).
This is odd since doing it manually using sudo -u \#10 -g \#10 mkdir
/sys/fs/cgroup/systemd/lxc/x1/x works fine.
--
You received this bug notification because you are a member
What does
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo netstat -lap| grep LISTEN
show now that you've updated bind9's configuration?
** This bug is no longer a duplicate of bug 1240757
Bridge not created if
What does
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo netstat -lap| grep LISTEN
show now that you've updated bind9's configuration?
** This bug is no longer a duplicate of bug 1240757
Bridge not created if
I believe what's happening is that systemd tries to mkdir init.scope
before the directory has been deleted and gets -EEXIST; then the kernel
finishes deleting it, then systemd tries to move itself to it but it is
gone.
Waiting for one more debugging build to verify.
--
You received this bug
I believe what's happening is that systemd tries to mkdir init.scope
before the directory has been deleted and gets -EEXIST; then the kernel
finishes deleting it, then systemd tries to move itself to it but it is
gone.
Waiting for one more debugging build to verify.
--
You received this bug
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
Quoting Kevin Dalley (1452...@bugs.launchpad.net):
> *** This bug is a duplicate of bug 1240757 ***
> https://bugs.launchpad.net/bugs/1240757
>
> I have now added
>
> listen-on-v6 { none; };
>
Hi Martin,
thanks for that info. During a reboot, lxc deletes the container's
cgroup, then recreates it. Is systemd expecting the cgroup it
previously created to stick around?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
Quoting Kevin Dalley (1452...@bugs.launchpad.net):
> *** This bug is a duplicate of bug 1240757 ***
> https://bugs.launchpad.net/bugs/1240757
>
> I have now added
>
> listen-on-v6 { none; };
>
Hi Martin,
thanks for that info. During a reboot, lxc deletes the container's
cgroup, then recreates it. Is systemd expecting the cgroup it
previously created to stick around?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
@arges,
did you want to push this patch into our package until it hits upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501651
Title:
ARM chroot issues: fatal error: rt_sigaction failure
@arges,
did you want to push this patch into our package until it hits upstream?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1501651
Title:
ARM chroot issues: fatal error:
Can you show which libvirt version you are using?
Can you show the results of:
ls -l /etc/apparmor.d/libvirt
ls -l /proc /proc/self /proc/self/attr
And then the following manual test:
cd /tmp
cat > testprofile << EOF
profile i_cant_be_trusted_anymore {
/etc/ld.so.cache
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
** This bug is no longer a duplicate of bug 1452601
vivid container's networking.service fails on boot with signal=PIPE
** This bug has been marked a duplicate of bug 1240757
Bridge not created if
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
** This bug is no longer a duplicate of bug 1452601
vivid container's networking.service fails on boot with signal=PIPE
** This bug has been marked a duplicate of bug 1240757
Bridge not created if
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
D'oh! thanks for that info. You are running bind9, which is causing
the conflict. To work around this, you can tell bind9 to not listen
on 10.0.3.1 - see
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
** This bug is no longer a duplicate of bug 1452601
vivid container's networking.service fails on boot with signal=PIPE
** This bug has been marked a duplicate of bug 1240757
Bridge not created if
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
D'oh! thanks for that info. You are running bind9, which is causing
the conflict. To work around this, you can tell bind9 to not listen
on 10.0.3.1 - see
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
** This bug is no longer a duplicate of bug 1452601
vivid container's networking.service fails on boot with signal=PIPE
** This bug has been marked a duplicate of bug 1240757
Bridge not created if
Is that really the only strace output you saw?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled
To manage
I believe the 'no such file or directory' is what qemu is reporting
about some device which openstack is trying to hand it.
Can you confirm that
/dev/hugepages/libvirt/qemu
exists (ls -l /dev/hugepages/libvirt)?
Try the following on your compute node to get strace output:
mv
Actually it seems reasonably likely that your problem is with:
-smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack
Nova,version=12.0.0,serial=e87d7510-5766-e35e-8016-ebeb55d7deff,uuid=3dceb341
-643d-492a-8a47-8154da341c02,family=Virtual Machine
because the smbios has spaces in the
** This bug is no longer a duplicate of bug 1512749
lxcbr0 dissappears on Ubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505576
Title:
internal error: Failed to initialize a valid
Thanks for that. I'm going to retitle this bug for the general topic
of properly reporting spaces in valius.
** Summary changed:
- Unable to set AppArmor profile for /usr/bin/kvm-spice
+ Unable to set AppArmor profile [...] no such file or directory
** Changed in: libvirt (Ubuntu)
** Description changed:
=
Bugs are not infrequently reported along the lines of
Unable to set Apparmor Profile for [emulator]: No such file or directory
- It is frequently (always?) the result of some value - a cdrom or disk
- file, smbios,
** This bug is no longer a duplicate of bug 1512749
lxcbr0 dissappears on Ubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1505576
Title:
internal error: Failed to
Ok, so the error msg is simply misleading - it says 'permission denied',
but the bridge does not exist.
Can you please show:
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo brctl show
and see if your container now starts?
Please also paste
Ok, so the error msg is simply misleading - it says 'permission denied',
but the bridge does not exist.
Can you please show:
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo brctl show
and see if your container now starts?
Please also paste
You're still getting
dnsmasq: failed to create listening socket for 10.0.3.1: Cannot
assign requested address
What does
sudo netstat -lap| grep LISTEN
show?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
You're still getting
dnsmasq: failed to create listening socket for 10.0.3.1: Cannot
assign requested address
What does
sudo netstat -lap| grep LISTEN
show?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Right, this is mentioned in the manpage. You can force environment
to be cleared by passing --clear-env. Actually setting HOME to what
a login shell would do would require lxc-attach to make assumptions
about the container. However you can
lxc-attach -n trusty-vimprobable --clear-env -- su -
Right, this is mentioned in the manpage. You can force environment
to be cleared by passing --clear-env. Actually setting HOME to what
a login shell would do would require lxc-attach to make assumptions
about the container. However you can
lxc-attach -n trusty-vimprobable --clear-env -- su -
*** This bug is a duplicate of bug 1512749 ***
https://bugs.launchpad.net/bugs/1512749
Because AIUI the upgrade will install the fix but not restart network
manager.
** This bug has been marked a duplicate of bug 1512749
lxcbr0 dissappears on Ubuntu 15.10
--
You received this bug
*** This bug is a duplicate of bug 1512749 ***
https://bugs.launchpad.net/bugs/1512749
Because AIUI the upgrade will install the fix but not restart network
manager.
** This bug has been marked a duplicate of bug 1512749
lxcbr0 dissappears on Ubuntu 15.10
--
You received this bug
I suspect this is a duplicate of bug 1512749
Are you using network-manager?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505576
Title:
internal error: Failed to initialize a valid firewall
please let us know if updating (and then perhaps rebooting) fixes it for
good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505576
Title:
internal error: Failed to initialize a valid firewall
Hi,
you're actually geting EPERM, which means lxcbr0 exists. Please show
the output of:
sudo lxc-start -n escale_build -F -l trace -o /dev/stdout
sudo brctl show
sudo ifconfig -a
sudo journalctl -u lxc-net
sudo systemd-detect-virt
--
You received this bug notification because you are a
Hi,
you're actually geting EPERM, which means lxcbr0 exists. Please show
the output of:
sudo lxc-start -n escale_build -F -l trace -o /dev/stdout
sudo brctl show
sudo ifconfig -a
sudo journalctl -u lxc-net
sudo systemd-detect-virt
--
You received this bug notification because you are a
Hi,
The fix was uploaded last week for acceptance by the SRU team. It's
waiting to be accepted into -proposed. Then it will need to be tested
to be accepted into -updates.
https://launchpad.net/ubuntu/precise/+queue?queue_state=1_text=lxc
--
You received this bug notification because you are
Ok. It was 'fix released' in cgmanager and lxc by working around it (not
enabling threading). It is invalid in lxcfs in xenial because we have
switched to glib and gdbus there. The libnih and dbus bugs are still open,
though in dbus it is wontfix from upstream. Since dbus is wontfix, I think
Hi,
The fix was uploaded last week for acceptance by the SRU team. It's
waiting to be accepted into -proposed. Then it will need to be tested
to be accepted into -updates.
https://launchpad.net/ubuntu/precise/+queue?queue_state=1_text=lxc
--
You received this bug notification because you are
Ok. It was 'fix released' in cgmanager and lxc by working around it (not
enabling threading). It is invalid in lxcfs in xenial because we have
switched to glib and gdbus there. The libnih and dbus bugs are still open,
though in dbus it is wontfix from upstream. Since dbus is wontfix, I think
1001 - 1100 of 15550 matches
Mail list logo
