discovery client doesn't handle some connectivity exceptions
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
New
|
Medium
|
Deepinder Setia | |||
R2.21.x |
Fix Committed
|
Medium
|
Deepinder Setia | |||
R2.22.x |
New
|
Medium
|
Deepinder Setia | |||
R3.0 |
Fix Committed
|
Medium
|
Deepinder Setia | |||
Trunk |
Fix Committed
|
Medium
|
Deepinder Setia |
Bug Description
Chhandak reported this:
-------
Hi Nipa,
In a 3 control node cluster for 2 of the control node IFMAP server list is empty. In turn control node does not have any connection with IFMAP server.
System has reach this state after restarting control node multiple time overnight using script with TOR Scale config.
Can you please have a look ?
Control Node1 : http://
Control Node3:http://
I don’t see IFMAP in service type for any of the discovery node
Node1: http://
Node2: http://
Node3: http://
-------
Looking at the system it appears that API server and IFMAP services are not getting published even though API server is up and running fine. These two services are published from within API server.
information type: | Proprietary → Public |
tags: | added: contrail-control |
Review in progress for https:/ /review. opencontrail. org/16689
Submitter: Deepinder Setia (<email address hidden>)