yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82554
[Bug 1877296] [NEW] Tunnel ports are not cleaned up with several ovs agents restart
Public bug reported:
If we update local_ip config value on several openvswitch agents and
restart them we may get tunnel ports with old local_ip(remote_ip)
setting are not cleaned up.
Before
Port "vxlan-c0a80006"
Interface "vxlan-c0a80006"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.0.7", out_key=flow, remote_ip="192.168.0.6"}
Port "vxlan-c0a89b04"
Interface "vxlan-c0a89b04"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.0.7", out_key=flow, remote_ip="192.168.155.4"}
After restart
Port "vxlan-c0a80006"
Interface "vxlan-c0a80006"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.0.7", out_key=flow, remote_ip="192.168.0.6"}
Port "vxlan-c0a89b04"
Interface "vxlan-c0a89b04"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.155.10", out_key=flow, remote_ip="192.168.155.4"}
Port "vxlan-c0a89b05"
Interface "vxlan-c0a89b05"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.155.10", out_key=flow, remote_ip="192.168.155.5"}
If agents restart one by one this issue does not appear.
Debug shows that during tunnel_sync
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L2240
rpc call
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/type_tunnel.py#L538
is getting interrupted http://paste.openstack.org/show/792876/ and some
tunnels are not proceeded properly.
Originally found on Queens version, but is reproduced with master code
and multinode devstack.
** 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/1877296
Title:
Tunnel ports are not cleaned up with several ovs agents restart
Status in neutron:
New
Bug description:
If we update local_ip config value on several openvswitch agents and
restart them we may get tunnel ports with old local_ip(remote_ip)
setting are not cleaned up.
Before
Port "vxlan-c0a80006"
Interface "vxlan-c0a80006"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.0.7", out_key=flow, remote_ip="192.168.0.6"}
Port "vxlan-c0a89b04"
Interface "vxlan-c0a89b04"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.0.7", out_key=flow, remote_ip="192.168.155.4"}
After restart
Port "vxlan-c0a80006"
Interface "vxlan-c0a80006"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.0.7", out_key=flow, remote_ip="192.168.0.6"}
Port "vxlan-c0a89b04"
Interface "vxlan-c0a89b04"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.155.10", out_key=flow, remote_ip="192.168.155.4"}
Port "vxlan-c0a89b05"
Interface "vxlan-c0a89b05"
type: vxlan
options: {df_default="true", egress_pkt_mark="0", in_key=flow, local_ip="192.168.155.10", out_key=flow, remote_ip="192.168.155.5"}
If agents restart one by one this issue does not appear.
Debug shows that during tunnel_sync
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L2240
rpc call
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/type_tunnel.py#L538
is getting interrupted http://paste.openstack.org/show/792876/ and
some tunnels are not proceeded properly.
Originally found on Queens version, but is reproduced with master code
and multinode devstack.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1877296/+subscriptions