Bug 1266221 - cluster is not accessible with rebooting one of the controller node
Summary: cluster is not accessible with rebooting one of the controller node
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
: 8.0 (Liberty)
Assignee: lpeer
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-24 19:51 UTC by bigswitch
Modified: 2016-04-27 04:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-30 17:04:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.