The RHEL OSP installer has l2pop on and turns on l3_ha if Neutron is installed on multiple controllers. However, due to RHBZ 1177611, l2pop and l3_ha do not work together. More precisely, routers will not work correctly and there will be no network connectivity whatsoever. Until this issue is resolved, l3_ha should never be turned on implicitly. If an admin would like to evaluate the feature, he should do so manually.
Verification steps: With a single controller: l3_ha should always be disabled l2_population should be set based on user input in the wizard With multiple controllers: If user sets l2_population to true, l3_ha should be set off in neutron config if user sets l2_population to false, l3_ha should be set on in neutron config
To validate l2pop is on: ml2_conf.ini on controllers: mechanism_drivers list should contain 'l2population', so should look like: mechanism_drivers = openvswitch,l2population On any node that has the OVS agent (This would include controllers): ovs_neutron_plugin.ini: l2_population = True To validate l3_ha is on: neutron.conf on controllers: l3_ha = True
Using RHEL OSP 6.0.1 RHEL 7.1 and deploying a 1x controller 1x compute node will result in both l2_population and l3_ha enabled as these are the defaults. I also confirmed l3 routing does not work completely with both of these features enabled...traffic cant traverse router and br-ex physical interface properly. I tried to disable l3_ha manually and through staypuft without success. Only option was redploy and ensure option is false.
https://github.com/theforeman/staypuft/pull/430
Following comment #6: Part 1: To validate l2pop is on: ml2_conf.ini on controllers: mechanism_drivers list should contain 'l2population', so should look like: mechanism_drivers = openvswitch,l2population Checking a controller: /etc/neutron/plugins/ml2/ml2_conf.ini:mechanism_drivers =openvswitch,l2population Good! Part2: On any node that has the OVS agent (This would include controllers): ovs_neutron_plugin.ini: l2_population = True No such line, in fact - the only l2_population line is: /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:# l2_population = False
Tested with ruby193-rubygem-staypuft-0.5.22-1.el7ost.noarch
Tested on ruby193-rubygem-staypuft-0.5.0-22-1.el7ost. According to Assaf l2_population must be enabled in /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini ,e.g. l2_population=True The only line related to l2_population in that file is: # l2_population = False Moving back to assign.
(In reply to Leonid Natapov from comment #12) > Tested on ruby193-rubygem-staypuft-0.5.0-22-1.el7ost. > > According to Assaf l2_population must be enabled in > /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini ,e.g. > l2_population=True > > The only line related to l2_population in that file is: > > # l2_population = False > > Moving back to assign. That's a new bug, then, not a reason to fail this BZ. This bz is specifically to prevent L3-HA and l2pop from being enabled together (by default, since a user can set these as they want in advanced parameters).
verified on ruby193-rubygem-staypuft-0.5.0-22-1.el7ost
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/RHSA-2015-0791.html