yahoo-eng-team team mailing list archive

[Radosław Piliszek <1846507@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This has been observed while testing CI IPv6.

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

linux bridge provides network for CI hosts using VXLAN 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.

** Affects: kolla-ansible
     Importance: Undecided
     Assignee: Radosław Piliszek (yoctozepto)
         Status: Opinion

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: ovs vxlan

** Also affects: neutron
   Importance: Undecided
       Status: New

-- 
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 bridge VXLAN over IPv4 using
  standard port

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

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

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

  linux bridge provides network for CI hosts using VXLAN 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.

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