yahoo-eng-team team mailing list archive

[Bernard Cafarelli <bcafarel@xxxxxxxxxx>]

** Tags added: ipv6

** Changed in: neutron
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1846507

Title:
  ovs VXLAN over IPv6 conflicts with linux native VXLAN over IPv4 using
  standard port

Status in kolla-ansible:
  Triaged
Status in neutron:
  Opinion

Bug description:
  This has been observed while testing CI IPv6.

  ovs-agent tries to run VXLAN over IPv6 (default port so 4789)

  linux provides network for CI hosts via native VXLAN (kernel interface of the vxlan type) over IPv4 using standard port (the 4789)
  kernel bound to IPv4-only UDP 0.0.0.0:4789

  ovs-agent:

  2019-10-02 19:42:55.073 6 ERROR
  neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-
  103d9f69-76c7-46bc-aeac-81b22af3e6b2 - - - - -] Failed to set-up vxlan
  tunnel port to fd::3

  vswitchd:

  2019-10-02T19:42:55.017Z|00059|dpif_netlink|WARN|Failed to create vxlan-srtluqpm3 with rtnetlink: Address already in use
  2019-10-02T19:42:55.053Z|00060|dpif|WARN|system@ovs-system: failed to add vxlan-srtluqpm3 as port: Address already in use
  2019-10-02T19:42:55.053Z|00061|bridge|WARN|could not add network device vxlan-srtluqpm3 to ofproto (Address already in use)

  For some reason this conflict does *not* arise when ovs is using IPv4
  tunnels (kinda counter-intuitively).

  Workarounded by using different port. This has no real life meaning
  (IMHO) but is undoubtedly an interesting phenomenon.

  Environment description:
  Distro: Ubuntu 18.04 (Bionic)
  Kernel: 4.15.0-65.74 (generic on x86_64)
  Neutron release: current master
  OVS: 2.11.0-0ubuntu2~cloud0 (from UCA - Ubuntu Cloud Archive for Train on Bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla-ansible/+bug/1846507/+subscriptions