[#VTN-130] VTN flow ID management fails when a new controller joins with the cluster.

[VTN-130] VTN flow ID management fails when a new controller joins with the cluster. Created: 29/Mar/16 Updated: 19/Oct/17 Resolved: 30/Mar/16
Status:	Resolved
Project:	vtn
Component/s:	VTN Manager
Affects Version/s:	unspecified
Fix Version/s:	None

Type:

Bug

Reporter:

Shigeru Yasuda

Assignee:

Unassigned

Resolution:

Done

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Operating System: All
Platform: All

External issue ID:

5616

Description

When a new controller node joins with the cluster and VTN Manager is installed in that node, it corrupts the next-flow-id container in the operational DS.
It results in failure of VTN flow ID management because the next-flow-id container keeps the flow ID for next allocation.

Comments

Comment by Shigeru Yasuda [ 29/Mar/16 ]

https://git.opendaylight.org/gerrit/36815 (master)

Comment by Shigeru Yasuda [ 30/Mar/16 ]

https://git.opendaylight.org/gerrit/36862 (stable/beryllium)

Generated at Wed Feb 07 20:48:07 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.

[VTN-130] VTN flow ID management fails when a new controller joins with the cluster. Created: 29/Mar/16 Updated: 19/Oct/17 Resolved: 30/Mar/16