touch-packages team mailing list archive

[Launchpad Bug Tracker <1402763@xxxxxxxxxxxxxxxxxx>]

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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1402763

Title:
  Multicast traffic not propating correctly over linux bridge

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  There's a lot of supposition in the title of this bug but its
  currently my best guess.

  In this deployment, I have a number of services running in LXC
  containers across multiple physical hosts; each service is clustered
  across three units, all on separate physical hosts, using corosync and
  pacemaker; when using multicast to support cluster communication, I
  occasionally see a container drop out of the cluster and use its
  isolation response (to shutdown all managed services); when using
  unicast I've not yet see this same problem.

  LXC containers are bridged to the main physical network using a linux
  bridge:

    eth0 <-> juju-br0 <-> vethXXX <-> | vethXXX |

  All MTU's are standard (1500).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: User Name 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Mon Dec 15 17:20:08 2014
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1402763/+subscriptions