Reviewed: https://review.openstack.org/270130
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=e2a37be73da7bbc0ab562eabef69bfe69dc7cfa1
Submitter: Jenkins
Branch: master
commit e2a37be73da7bbc0ab562eabef69bfe69dc7cfa1
Author: Oleg Bondarev <obonda...@mirantis.com>
Date: Wed Jan 20 13:53:20 2016 +0300
OVS agent should fail if it can't get DVR mac address
Currently agent will fall back to non-dvr mode in case it can't.
However neutron server does not check dvr mode of ovs agents when
scheduling routers. So in a DVR enabled cluster all ovs agents
should run in DVR mode. Otherwise it will lead to undefined
behavior which is hard to debug.
Closes-Bug: #1536110
Change-Id: I6c31aabf1852c688e9c27fc1859d3fdd830caa68
** 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/1536110
Title:
OVS agent should fail if can't get DVR mac address
Status in neutron:
Fix Released
Bug description:
If ovs agent is configured to run in dvr mode it has to get it's
unique mac address from server on startup . In case it cannot get it
after several attempts (commit
51303b5fe4785d0cda76f095c95eb4d746d7d783) due to some error, it falls
back to non-dvr mode.
The question is what is the purpoise of ovs agent to be running in
non-dvr mode while it was configured for dvr? Server code does not
handle ovs agent 'in_distributed_mode' flag in any way and will
continue scheduling dvr routers to such nodes. This may lead to
connectivity issues which are hard to debug.
Example:
2016-01-12 11:29:15.186 16238 WARNING
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_dvr_neutron_agent
[req-e3b3643d-6976-4656-b247-ab291e6a4b27 - - - - -] L2 agent could
not get DVR MAC address at startup due to RPC error. It happens when
the server does not support this RPC API. Detailed message: Remote
error: DBConnectionError (_mysql_exceptions.OperationalError) (2013,
"Lost connection to MySQL server at 'reading initial communication
packet', system error: 0")
There were some issues with mysql on startup which led to half of ovs
agents running in non-dvr mode silently.
The proposal is to fail in case agent cannot operate in the mode it
was configured to.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1536110/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
