yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #71831
[Bug 1756406] Re: DVR: Fix dvr mac address format to be backward compatible with non native openflow interface
Reviewed: https://review.openstack.org/553870
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6b13cf0bee67e6196201e7863b1facce54b6d6f6
Submitter: Zuul
Branch: master
commit 6b13cf0bee67e6196201e7863b1facce54b6d6f6
Author: Swaminathan Vasudevan <SVasudevan@xxxxxxxx>
Date: Wed Mar 14 16:59:32 2018 -0700
DVR: Fix mac format for backward compatibility with vsctl api
Fix the mac address format for backward compatibility with
vsctl ovs api
Closes-Bug: #1756406
Change-Id: I3ba11fae433b437d9d3a0b12dd8a11fe1b35046a
** 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/1756406
Title:
DVR: Fix dvr mac address format to be backward compatible with non
native openflow interface
Status in neutron:
Fix Released
Bug description:
DVR MAC address is configured on the server for every node that is
configured to run in one of the dvr agent modes ( dvr,dvr_snat and
dvr_no_external).
The DVR MAC addresses are stored in the 'AA-BB-CC-DD-EE-FF' format.
When the agent tries to configure the DVR MAC addresses into the
openflow rules using the native interface drivers, they are ok.
But when used with the non native interface drivers this throws an
error as shown below.
Unable to execute ['ovs-ofctl', 'add-flows', 'br-vlan1078', '-'].
Exception: Exit code: 1; Stdin:
hard_timeout=0,idle_timeout=0,priority=2,table=3,cookie=12002607947458125225,dl_src=FA-16
-3F-AA-78-20,actions=output:2; Stdout: ; Stderr: ovs-ofctl: -:1: FA-16
-3F-AA-78-20: invalid Ethernet address.
This is also seen in the Master branch.
So to provide backward compatibility, we need to add a patch to change the format of the MAC before it is handed over to the openflow interface driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1756406/+subscriptions
References