ml2 mechanism is call again if it calls continue binding

[Bo Chi]

if there're multiple mechanism driver configured, and the first driver call context.continue_binding at level 0, it will be called again on level 1.

this is because parameter "driver" passed to _check_driver_to_bind is not correct, which should be dirver name instead of driver itself

[Akihiro Motoki (amotoki)]

https://review.openstack.org/#/c/530357/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/530357
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=892c1ec6900c7834964dd912cadab5d7ee3d4f62
Submitter: Zuul
Branch: master

commit 892c1ec6900c7834964dd912cadab5d7ee3d4f62
Author: Bo Chi <email address hidden>
Date: Thu Dec 28 21:35:31 2017 +0800

    fix same mechanism driver called twice bug

    when a mechinism driver calls context.continue_binding to
    continue binding, it will be called again because
    _check_driver_to_bind compares driver name with driver.

    Closes-Bug: #1745572
    Change-Id: I62b32c9b9d01dd929fe8cd3634c78dc0cbe325b6

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 12.0.0.0rc1 release candidate.