** No longer affects: lxc (Ubuntu)
--
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/1402763
Title:
Multicast traffic not propating correctly over linux bridge
To manage notifications abo
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
--
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/1402763
Title:
Multicast traffic not propating correctly over linux bridge
Have the same issue not juju related at all : created a single LXC container on
ubuntu precise :
Here are the value for multicast querier
cat /sys/devices/virtual/net/lxcbr0/bridge/multicast_querier
1
>From container : ping 239.255.255.250 (UPnP adress) does not work but
works fine on host. Othe
Stephane
The network itself is pretty stock; the mtu on the switches is set to
9000; other than that its pretty much the standard cisco configuration
for the switch model.
I have the full details (but can't put them here :-)).
--
You received this bug notification because you are a member of Ub
** Tags added: lxc network
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => Medium
--
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/bu
Anything else that's special on that network, e.g. non-standard MTU?
--
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/1402763
Title:
Multicast traffic not propating correctly over linux b
Even post toggling the querier off/no, multicast is still unreliable,
with cluster members failing to transmit data successfully to each
other.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
Just to fill in a bit more detail, the physical hosts have multiple lxc
containers (~3 each), any of which will be participating in a different
multicast group; containers in the same group are spread across
different physical hosts.
--
You received this bug notification because you are a member
I enabled the multicast_querier using a udev rule for juju-br0; however
physical host reboots are still resulting in impact lxc containers not
re-joining the cluster; toggling the querier off/on again resolves the
issue so I'm guessing some sort of race.
** Tags added: apparmor apport-collected
*
** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
--
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/1402763
Title:
Multicast traffic not propating correctly over linux bri
For context:
http://en.wikipedia.org/wiki/IGMP_snooping#IGMP_querier
** Also affects: juju-core
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
Things appear to be somewhat random; however setting the
multicast_querier flag to 1 resulted in all my clustered spring back to
life:
for i in `seq 0 10`; do juju ssh $i "echo -n 1 | sudo tee
/sys/devices/virtual/net/juju-br0/bridge/multicast_querier"; done
Juju creates a bridge where this is no
** 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/1402763
Title:
Multicast traffic not propating correctly over
I've done a bit more testing, and here are my observations:
1) rebooting a container internally/stop-start externally using lxc-*
Works OK - container re-joins the corosync cluster just fine.
2) rebooting the physical host
Fails - containers never re-join the corosync cluster and perform the
co
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
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/1402763
T
15 matches
Mail list logo
