Description of problem: Neutron Mechanism Drivers for the overcloud aren't configured. I don't know if this is bug worthy but filing this so it can be tracked (looked at this thanks to Tim Swanson comments @ [1]). The tripleo heat templates say 'openvswitch' for the default for this value (description of what this config is at [2]). Whilst we do correctly set the hiera data passed to puppet, we don't consume it, meaning the deployment config is like: ./plugin.ini:20:mechanism_drivers =openvswitch,linuxbridge ./plugins/ml2/ml2_conf.ini:20:mechanism_drivers =openvswitch,linuxbridge which is the puppet-neutron module default. Even though we end up with correct behaviour (since afaik we've only ever used openvswitch for ml2 here) I think the bug is the expectation that the config item is configurable via the tripleo heat template param, which it is not in reality (tripleo image element deploys do consume and set this in the pass though data) [1] https://review.openstack.org/#/c/198754/10 [2] http://docs.openstack.org/kilo/config-reference/content/networking-options-plugins-ml2.html Version-Release number of selected component (if applicable): How reproducible: every time Steps to Reproduce: 1. deploy an overcloud, try to set NeutronMechanismDrivers (or even just leave the default, which is 'openvswitch') 2. [root@overcloud-controller-0 ~]# grep -rn 'mechanism_drivers' /etc/neutron/* 3. profit ("=openvswitch,linuxbridge") Actual results: ./plugins/ml2/ml2_conf.ini:20:mechanism_drivers =openvswitch,linuxbridge Expected results: Would expect the mechanism_driver to be set to 'openvswitch' only as that is the tht default Additional info:
literally one line fixup https://review.openstack.org/#/c/214649/
upstream bug at https://bugs.launchpad.net/tripleo/+bug/1488176
*** Bug 1261054 has been marked as a duplicate of this bug. ***
Verified: Environment: openstack-tripleo-heat-templates-0.8.6-64.el7ost.noarch grep -rn ^mechanism_drivers /etc/neutron/plugins /etc/neutron/plugins/ml2/ml2_conf.ini:20:mechanism_drivers =openvswitch The mechanism_driver is set to 'openvswitch' only as expected.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1862