Description of problem: If bridge_name parameter is set to NULL, external_network_bridge value is set to br-ex in /etc/neutron/l3_agent.ini at each puppet update. This value should be parameterized or default to blank. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Set bridge_name parameter to blank in neutron network storage group 2. Add a host to neutron network host group 3. Run puppet agent -tv 4. Check external_network_bridge value in /etc/neutron/l3_agent.ini Actual results: value set to br-ex Expected results: value not set Additional info:
I'm trying to verify with :openstack-foreman-installer-1.0.0-1.el6ost.noarch I've changed the parameter bridge_name in neutron-controller host group from : bridge_interface=eth --> bridge_interface= <Blank> After deployment looking at : vi /etc/neutron/l3_agent.ini Shows: # external_network_bridge = br-ex (the value is comment-out with '#') I'm not sure if this bug should be verified or reassigned.
After discussion with ajeain we realized the parameter should not remain with it's default value and should be changed. from : # external_network_bridge = br-ex to: external_network_bridge =
(In reply to Omri Hochman from comment #3) > After discussion with ajeain we realized the parameter should not remain > with it's default value and should be changed. Crag, is that right?
Whatever is set as external_network_bridge blank in the Neutron Networker Host Group param page will populate external_network_bridge in /etc/neutron/l3_agent.ini . Leave this as blank to set it as blank in the .ini file (meaning use a provider network), or set it to br-ex if that is desired. NOTE: Please test with openstack-foreman-installer-1.0.1-1.el6ost.noarch.rpm, different results will occur with an earlier version.
Verified with :openstack-foreman-installer-1.0.1-2.el6.noarch
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://rhn.redhat.com/errata/RHBA-2014-0046.html