devstack

The ML2 devstack integration doesn't set mechanism_drivers correctly

Bug #1208557 reported by Kyle Mestery
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Fix Released
Undecided
Kyle Mestery

Bug Description

Currently, there are 2 issues with the ML2 devstack work:

1) Q_ML2_PLUGIN_MECHANISM_DRIVERS is set at the top, but incorrectly to Q_PLUGIN_MECHANISM_DRIVERS.
2) The ML2 code never updates mechanism_drivers in the config file.

These are both trivial to fix.

Kyle Mestery (mestery)
Changed in devstack:
assignee: nobody → Kyle Mestery (mestery)
assignee: Kyle Mestery (mestery) → nobody
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

Fix proposed to branch: master
Review: https://review.openstack.org/40260

Changed in devstack:
assignee: nobody → Kyle Mestery (mestery)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (master)

Reviewed: https://review.openstack.org/40260
Committed: http://github.com/openstack-dev/devstack/commit/3ea28ece4a71b0137050314af0e4f3e55046db11
Submitter: Jenkins
Branch: master

commit 3ea28ece4a71b0137050314af0e4f3e55046db11
Author: Kyle Mestery <email address hidden>
Date: Mon Aug 5 12:24:32 2013 +0000

    Correctly setup ML2 mechanism_drivers

    The ML2 code in devstack was not correctly configuring the mechanism_drivers
    when asked to do so. This corrects the typo in the variable assignment, and
    also actually sets these in the plugin configuration file.

    Fixes bug 1208557

    Change-Id: I3746ca099f45d44dcf1cc2ca1c3726745b8e8a1d

Changed in devstack:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.