Now that we have a config knob for this, I believe we can claim it's
fixed from neutron side. I understand there are some hard feelings about
the solution, and we can revisit the way we tackle it later, but from
short sight it seems like we can close the bug.
** Changed in: neutron
Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka)
** Changed in: neutron
Status: Confirmed => 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/1450067
Title:
Server with ML2 & L3 service plugin exposes dvr extension even if OVS
agent is unused
Status in neutron:
Fix Released
Bug description:
In a deployment using the L3 service plugin, the DVR extension is
always declared as available, this is even if the ML2 OVS mech driver
is not configured. Deployments could be using the LB mech driver or
others. Not only is the extension declared, DVR router creation is not
blocked. We should not rely only on documentation, but additionally
provide expected behavior (Fail gracefully, not expose the extension).
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1450067/+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
