Bug 1207284

Summary:	l2pop and l3-ha should never be turned on together
Product:	Red Hat OpenStack	Reporter:	Assaf Muller <amuller>
Component:	ruby193-rubygem-staypuft	Assignee:	Scott Seago <sseago>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.0 (Juno)	CC:	aberezin, ajeain, amuller, avozza, dmacpher, ktenzer, mburns, nyechiel, oblaut, rhos-maint, sasha, sputhenp, sseago, yeylon
Target Milestone:	z2	Keywords:	ZStream
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ruby193-rubygem-staypuft-0.5.0-22-1.el7ost	Doc Type:	Bug Fix
Doc Text:	Incompatibilities between l2pop and l3_ha drivers caused errors with networking when both were enabled. This fix disables l3_ha if l2pop is enabled as part of the default flow. Networking now works as long as the values are not incorrectly set in Advanced Parameters.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-07 15:09:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Assaf Muller 2015-03-30 15:40:47 UTC

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.

Comment 5 Mike Burns 2015-03-31 14:39:34 UTC

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

Comment 6 Assaf Muller 2015-03-31 15:09:40 UTC

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

Comment 7 ktenzer 2015-03-31 16:09:02 UTC

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.

Comment 8 Scott Seago 2015-03-31 16:46:29 UTC

https://github.com/theforeman/staypuft/pull/430

Comment 10 Alexander Chuzhoy 2015-04-01 18:44:23 UTC

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

Comment 11 Alexander Chuzhoy 2015-04-01 18:45:53 UTC

Tested with ruby193-rubygem-staypuft-0.5.22-1.el7ost.noarch

Comment 12 Leonid Natapov 2015-04-05 09:17:54 UTC

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.

Comment 13 Mike Burns 2015-04-05 15:27:45 UTC

(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).

Comment 14 Leonid Natapov 2015-04-06 04:48:36 UTC

verified on ruby193-rubygem-staypuft-0.5.0-22-1.el7ost

Comment 16 errata-xmlrpc 2015-04-07 15:09:05 UTC

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