Bug 1266221

Summary:	cluster is not accessible with rebooting one of the controller node
Product:	Red Hat OpenStack	Reporter:	bigswitch <rhosp-bugs-internal>
Component:	openstack-neutron	Assignee:	lpeer <lpeer>
Status:	CLOSED NOTABUG	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	chrisw, nyechiel, yeylon
Target Milestone:	---
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-30 17:04:00 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 bigswitch 2015-09-24 19:51:50 UTC

Description of problem:

With 100 router interfaces present across 3 controller nodes (L3 agent) , after rebooting one of the node , cluster is not accessible 
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens
Unable to establish connection to http://10.8.68.111:5000/v2.0/tokens

Version-Release number of selected component (if applicable):

RHOSP 7.0
How reproducible:

Steps to Reproduce:
1.Create a 100 Router interfaces distributed across 3 L3 agents (controller nodes)
2.reboot one of the controller node
3.Neutron agent-list or openstack dashboard is not accessible

Actual results:


Expected results:


Additional info:

sos report link is below

Comment 2 bigswitch 2015-09-24 21:24:28 UTC

We will provide more details , Still debugging in our side to make sure VLANS are proper.

Comment 3 bigswitch 2015-09-30 17:04:00 UTC

This was due to some VLAN mismatch with our setup , So closing this bug.