yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #73539
[Bug 1778643] Re: DVR: Fip gateway port is tagged as DEAD port by OVS when external_bridge is configured
Reviewed: https://review.openstack.org/578002
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b2b42296965d8d339f06e62bd76ff81c0b746777
Submitter: Zuul
Branch: master
commit b2b42296965d8d339f06e62bd76ff81c0b746777
Author: Swaminathan Vasudevan <SVasudevan@xxxxxxxx>
Date: Mon Jun 25 23:25:19 2018 -0700
DVR: FIP gateway port is tagged as DEAD port by OVS with external-bridge
FIP agent gateway port is tagged as a DEAD port by OVS when external
bridge is configured in neutron.
When external bridge is configured, the vlan tag should be removed
after the port is plugged in.
This patch fixes the issue.
Change-Id: I969b9d7e7cef4beff526a2b26de3f1a9f9de4c1c
Closes-Bug: #1778643
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1778643
Title:
DVR: Fip gateway port is tagged as DEAD port by OVS when
external_bridge is configured
Status in neutron:
Fix Released
Bug description:
When external bridge is configured in Neutron, the FIP Agent Gateway
port 'fg-' is tagged as a DEAD port with Vlan id of 4095.
This issue is seen in Pike.
It seems that there was fix that recently merged in neutron shown below
https://review.openstack.org/#/c/564825/10
Based on this patch, the 4095 vlan tag for the 'qg-' is removed when
external bridge is configured. But it has not been handled for the DVR
FIP agent gateway port.
So we are seeing the port as DEAD always, when external bridge such as
'br-vlan1087' is configured.
Bridge "br-vlan1087"
Port "br-vlan1087"
Interface "br-vlan1087"
type: internal
Port "vlan1087"
Interface "vlan1087"
Port "fg-0a4a425d-d5"
tag: 4095
Interface "fg-0a4a425d-d5"
type: internal
ovs_version: "2.7.0"
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1778643/+subscriptions
References