I have a ton of leaked mongod processes, but also apparently leaking virtual ethernet adapters:
$ ifconfig | grep veth veth5699cea6 Link encap:Ethernet HWaddr ca:70:40:dc:9d:32 veth63846fbb Link encap:Ethernet HWaddr f2:8b:bb:3b:08:9a veth9111be0e Link encap:Ethernet HWaddr be:a3:41:be:fd:0c veth992938f8 Link encap:Ethernet HWaddr 52:78:6b:1b:ac:97 vethea0be4ac Link encap:Ethernet HWaddr ce:72:b0:7f:81:e4 Are we creating virtual adapters during tests? That seems pretty egregious. On Fri, Apr 8, 2016 at 6:13 PM Horacio Duran <[email protected]> wrote: > Hey, this is more of an open question/sharing. > I was a good half hour trying to find why reboot test was timeouting and > found that I had a couple of lxcs that I dont recall creating (at least one > of them was a juju api server) and a good 5-8 mongos running. > I killed the test, the mongos and the lxcs and magic, the reboot tests ran > well. > Did anyone else detect this kind of behavior? I believe either destroy (I > deployed a couple of times earlier and destroyed) or the tests are leaking, > at least, lxcs Ill try to repro later but so far I would like some one > else's input. > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
