Bug 1268244

Summary:	All l3 agents go to standby ha_state after restarting haproxy resource triggered by incomplete cleanup.
Product:	Red Hat OpenStack	Reporter:	Miguel Angel Ajo <majopela>
Component:	openstack-neutron	Assignee:	Miguel Angel Ajo <majopela>
Status:	CLOSED ERRATA	QA Contact:	Toni Freger <tfreger>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	abeekhof, amuller, bperkins, chrisw, fdinitto, jlibosva, jmelvin, majopela, mandreou, mangelajo, mburns, mcornea, michele, mlopes, nyechiel, rhel-osp-director-maint, rscarazz, sclewis, tfreger, vincent, yeylon
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-2015.1.1-12.el7ost	Doc Type:	Bug Fix
Doc Text:	Prior to this update, the netns pacemaker OCF resource did not perform a full cleanup of the neutron netns services. As a result, some of those services were orphaned, and were never restored by they l3-agent because were seen as running, but were actually disconnected. This update addresses this by adding the missing cleanup steps to the netns cleanup OCF resource.	Story Points:	---
Clone Of:	1266910	Environment:
Last Closed:	2015-12-21 16:58:40 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:
Bug Depends On:	1266910
Bug Blocks:

Comment 4 Toni Freger 2015-12-09 10:35:42 UTC

Verified with virt env. installed with OSP-d 
3-Controllers - HA
1-Ceph
1-Compute

openstack-tripleo-common-0.0.1.dev6-5.git49b57eb.el7ost.noarch
openstack-tripleo-heat-templates-0.8.6-87.el7ost.noarch
openstack-tripleo-0.0.7-0.1.1664e566.el7ost.noarch
openstack-tripleo-image-elements-0.9.6-10.el7ost.noarch
openstack-tripleo-puppet-elements-0.0.1-5.el7ost.noarch

openstack-neutron-2015.1.2-2.el7ost.noarch


Steps to Reproduce (tested several times):
1. Deploy overcloud with 3 controllers 
2. Create tenant network, external network and router
3. Run pcs resource restart haproxy-clone on one of the controllers
4. Check l3 agents for the router 
5. Router external connectivity tested 
6. Router fail-over triggered and different l3 agent become an active. 
7. Router external connectivity tested

Comment 6 errata-xmlrpc 2015-12-21 16:58:40 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://access.redhat.com/errata/RHBA-2015:2652