| 2019-10-03 14:33:05 |
Radosław Piliszek |
bug |
|
|
added bug |
| 2019-10-03 14:33:22 |
Radosław Piliszek |
bug task added |
|
neutron |
|
| 2019-10-03 14:35:35 |
Radosław Piliszek |
kolla-ansible: status |
Triaged |
Opinion |
|
| 2019-10-03 14:35:41 |
Radosław Piliszek |
kolla-ansible: importance |
Wishlist |
Undecided |
|
| 2019-10-03 14:39:33 |
Radosław Piliszek |
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 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. |
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. |
|
| 2019-10-03 14:49:23 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
| 2019-10-03 16:26:56 |
Radosław Piliszek |
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. |
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.
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) |
|
| 2019-10-03 16:28:36 |
Radosław Piliszek |
summary |
ovs VXLAN over IPv6 conflicts with linux bridge VXLAN over IPv4 using standard port |
ovs VXLAN over IPv6 conflicts with linux native VXLAN over IPv4 using standard port |
|
| 2019-10-03 16:29:12 |
Radosław Piliszek |
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.
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) |
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) |
|
| 2019-10-03 16:33:38 |
Radosław Piliszek |
attachment added |
|
ss non-listening https://bugs.launchpad.net/neutron/+bug/1846507/+attachment/5294017/+files/ss.txt |
|
| 2019-10-03 16:33:59 |
Radosław Piliszek |
attachment added |
|
ss listening https://bugs.launchpad.net/neutron/+bug/1846507/+attachment/5294018/+files/ss_l.txt |
|
| 2019-10-03 16:41:31 |
Radosław Piliszek |
attachment added |
|
fed to ovs-agent https://bugs.launchpad.net/neutron/+bug/1846507/+attachment/5294019/+files/neutron.conf |
|
| 2019-10-03 16:41:46 |
Radosław Piliszek |
attachment added |
|
fed to ovs-agent https://bugs.launchpad.net/neutron/+bug/1846507/+attachment/5294020/+files/ml2_conf.ini |
|
| 2019-10-03 17:15:06 |
Radosław Piliszek |
kolla-ansible: status |
Opinion |
Triaged |
|
| 2019-10-03 17:15:13 |
Radosław Piliszek |
kolla-ansible: importance |
Undecided |
Wishlist |
|
| 2019-10-04 15:00:48 |
Bernard Cafarelli |
tags |
ovs vxlan |
ipv6 ovs vxlan |
|
| 2019-10-04 15:01:03 |
Bernard Cafarelli |
neutron: status |
New |
Opinion |
|
| 2019-10-08 16:47:48 |
Radosław Piliszek |
kolla-ansible: status |
Triaged |
Opinion |
|
| 2019-10-08 16:47:56 |
Radosław Piliszek |
kolla-ansible: importance |
Wishlist |
Undecided |
|
| 2019-10-08 16:48:01 |
Radosław Piliszek |
kolla-ansible: milestone |
9.0.0 |
|
|
| 2019-10-08 16:48:07 |
Radosław Piliszek |
kolla-ansible: assignee |
Radosław Piliszek (yoctozepto) |
|
|
| 2019-11-26 06:17:25 |
Xing Zhang |
bug |
|
|
added subscriber Xing Zhang |
