Detect duplicate subscribe for routing-instance on CN
Bug #1431025 reported by
Nischal Sheth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.1 |
Fix Released
|
Wishlist
|
Nischal Sheth | |||
Trunk |
Fix Released
|
Wishlist
|
Nischal Sheth |
Bug Description
It will be useful to detect a duplicate subscribe on the CN, log an error
or warning message and trigger a close of the xmpp connection, so that
both sides can start with a clean slate. The duplicate subscribe could
be due to a bug on the agent side.
Another possibility would be to synthesize an unsubscribe, and queue up
a deferred subscribe for the routing-instance in question. The impact is
more contained, but there's a chance that the 2 sides won't still be in sync. Hence closing the connection is the preferred approach.
description: | updated |
description: | updated |
summary: |
- Detect duplicate subscribe for routing-instance on the CN + Detect duplicate subscribe for routing-instance on CN |
information type: | Proprietary → Public |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/8148
Submitter: Nischal Sheth (<email address hidden>)