SM: discovery server ip should be set to localhost on all services .conf files, if available
Bug #1545144 reported by
Senthilnathan Murugappan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.0 |
New
|
Low
|
Abhay Joshi | |||
| Trunk |
New
|
Low
|
Abhay Joshi | |||
Bug Description
SM: discovery server ip should be set to localhost on all contrail services .conf files, if there is a discovery server available in the localhost.
SM provisions all the .conf files to point to the last config node which could lead to a single point of failure if that config node is down.
This is also an issue with Fab provisioned setup where in services other than config point to first node in the cluster.
Revision history for this message
| Ignatious Johnson Christopher (ijohnson-x) wrote | #1 |
| Changed in juniperopenstack: | |
| importance: | Critical → Medium |
Revision history for this message
| Dheeraj Gautam (dgautam) wrote | #2 |
To post a comment you must log in.
Customers usually deploy contrail HA, if they have more than one config node. However for those customers who don't use contrail HA but still have multiple config nodes, and some other roles also share the same set of node, it is good to keep localhost as Discovery IP.
So reducing the importance to Medium