Dan Kegel, would utilizing the Raring enablement stack in Precise work
for you as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack ?
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug
(Marking fix-released for lxc per comment #19)
** Changed in: lxc (Ubuntu)
Status: Triaged = Fix Released
--
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/1065589
Title:
initctl
Where does this stand? A fully updated 12.04.1 system is still seeing lots of
interfaces;
2015 network-interface
4028 network-interface-security
and toggling an lxc container up and down four times seemed to result in
one extra network-interface and four extra network-interface-security's.
I fixed the userspace side of this in 13.04 and the 3.8 kernel contains the
matching kernel fix.
I could probably backport the fix to 12.04, though it won't work until the
13.04 kernel is backported and people explicitly move to it.
--
You received this bug notification because you are a
Thanks.
--
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/1065589
Title:
initctl list shows 11974 instances of network-interface-security
after two days of uptime
To manage
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1065589
Title:
initctl list shows 11974 instances of
I'm running ltp against my proposed patch, and will send it to netdev
(per the email thread) later today.
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Tags added: patch
--
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/1065589
Title:
initctl list shows 11974 instances of network-interface-security
after two days of uptime
To
Running this script periodically seems to work around the problem. Only
lightly tested.
** Attachment added: gc.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1065589/+attachment/3396509/+files/gc.sh
--
You received this bug notification because you are a member of Ubuntu
Server
Oops, that only deleted one of the jobs. This draft deletes both.
** Attachment added: gc.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1065589/+attachment/3396518/+files/gc.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
@Dan,
note that you can also compare the list of running 'network-interface'
jobs to the veth's in /sys/class/net/. For those which are not there,
you can remove the network-interface job using
sudo initctl emit net-device-removed INTERFACE=$thenicyoufound
--
You received this bug notification
Once more with feeling.
** Attachment added: bug1065589-gc.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1065589/+attachment/3396522/+files/bug1065589-gc.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Email thread about a potential kernel patch to solve the problem:
http://lists.linuxfoundation.org/pipermail/containers/2012-October/030519.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Alas, that archive doesn't show attachments. For the record, is there
a better archive somewhere?
--
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/1065589
Title:
initctl list shows
Hm, I didn't know it did that. The patch wasn't even an attachment,
just inline.
I'll attach the new version here. There is another archive at sf.net,
but it doesn't seem to have oct 12 messages yet.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Patch added:
0001-dev_change_net_namespace-send-a-KOBJ_REMOVED-to-orig.patch
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1065589/+attachment/3396958/+files/0001-dev_change_net_namespace-send-a-KOBJ_REMOVED-to-orig.patch
--
You received this bug notification because you are a
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
--
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/1065589
Title:
initctl list shows 11974 instances of
Note that the count goes up by 1 for each container. But each container
has 2 veths.
My guess is that when lxc passes one of the 2 veths into the container,
we need to emit a net-device-removed signal for the passed-in device.
--
You received this bug notification because you are a member of
Yup, I can reproduce this. However I believe the bug is in the init
script, not in lxc. The veth interfaces are not around.
** 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
Ah, no, both veths have a network-interface job sticking around.
Could this be seen as a kernel/udev bug, that when they veth is
destroyed (and maybe even when passed to a new netns) a uevent should be
sent?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This can be worked around by manually stopping the jobs, for instance:
sudo stop network-interface-security JOB=network-interface
INTERFACE=vethCEDGKQ
So lowering priority (per guidelines) since there is a workaround.
** Changed in: lxc (Ubuntu)
Importance: High = Medium
--
You received
I've opened bug 1065684 to handle the network-interface-security jobs.
Those can just be made to go away immediately.
THe network-interface jobs are a bit more contraversial. The question
is whether the kernel should emit a signal, or whether lxc should, when
a veth is moved to another network
Looking at the kernel source, I believe the uevent is being sent. I
think udev (or upstart-udev-bridge) may be tossing the event because the
device is no longer valid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Running 'udevadm monitor' while starting and stopping a container gives:
KERNEL[17237.641503] add /devices/virtual/net/veth7t59jJ (net)
KERNEL[17237.644300] add /devices/virtual/net/veth7t59jJ/queues/rx-0
(queues)
KERNEL[17237.644577] add
24 matches
Mail list logo
