yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #52704
[Bug 1595574] [NEW] VXLan fails to be created between dhcp and compute node
Public bug reported:
I have strange issue. VXLan fails to connect dhcp agent and compute
node. VXLan compute-compute builds successfully. No log ERROR or even
WARNING.
compute node:
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port "vxlan-c0a86424"
Interface "vxlan-c0a86424"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="192.168.100.29", out_key=flow, remote_ip="192.168.100.36"}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
DHCP agent node:
Bridge br-tun
fail_mode: secure
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "vxlan-c0a8641d"
Interface "vxlan-c0a8641d"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.29"}
Port "vxlan-c0a86424"
Interface "vxlan-c0a86424"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.36"}
Port br-tun
Interface br-tun
type: internal
I have 2 vms, at compute .36 and .29. As you can see, compute doesn't have tunnel exit from dhcp agent node.
This was deployed by latest master kolla, which translates to latest master neutron.
** Affects: neutron
Importance: Undecided
Assignee: Darek Smigiel (smigiel-dariusz)
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/1595574
Title:
VXLan fails to be created between dhcp and compute node
Status in neutron:
New
Bug description:
I have strange issue. VXLan fails to connect dhcp agent and compute
node. VXLan compute-compute builds successfully. No log ERROR or even
WARNING.
compute node:
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port "vxlan-c0a86424"
Interface "vxlan-c0a86424"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="192.168.100.29", out_key=flow, remote_ip="192.168.100.36"}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
DHCP agent node:
Bridge br-tun
fail_mode: secure
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "vxlan-c0a8641d"
Interface "vxlan-c0a8641d"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.29"}
Port "vxlan-c0a86424"
Interface "vxlan-c0a86424"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.36"}
Port br-tun
Interface br-tun
type: internal
I have 2 vms, at compute .36 and .29. As you can see, compute doesn't have tunnel exit from dhcp agent node.
This was deployed by latest master kolla, which translates to latest master neutron.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1595574/+subscriptions
Follow ups