discovery client service-in-use-list incorrect
Bug #1552277 reported by
Deepinder Setia
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.0 |
Fix Committed
|
Low
|
Nipa | |||
| Trunk |
Fix Committed
|
Low
|
Nipa | |||
Bug Description
Following sequence causes discovery C++ clients to send extra publisher in service-in-use-list
1) Agent connects to two control nodes (information received in subscribe response)
2) One of the control is administratively marked down
3) Discovery send a new control node. Agent disconnects from the down CN and connects to newly assigned CN
4) service in use list now includes two currently connected CN plus the original CN that is down. Thus Agents is sending 3 CN inside service-in-use-list instead of 2.
| Changed in juniperopenstack: | |
| importance: | Undecided → Low |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote [Review update] master | #1 |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote | #3 |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote [Review update] R3.0 | #5 |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #7 |
| Changed in juniperopenstack: | |
| milestone: | none → r3.1.0.0-fcs |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote | #9 |
| information type: | Proprietary → Public |
To post a comment you must log in.
Review in progress for https:/
Submitter: Nipa Kumar (<email address hidden>)