Bug 1998 - Fixing Bridge Set-Controller operation failure 99/11399/1
authorMadhu Venugopal <mavenugo@gmail.com>
Sat, 20 Sep 2014 12:36:17 +0000 (05:36 -0700)
committerMadhu Venugopal <mavenugo@gmail.com>
Sat, 20 Sep 2014 12:36:17 +0000 (05:36 -0700)
commit941a0858be834736ae56ab397a98f6c5b6ed2a5d
tree6127861f5c6819c5510f46b57b1606692dfcfd77
parent53c4d5593e96a8fda202084db3a6c9ecfd22e613
Bug 1998 - Fixing Bridge Set-Controller operation failure

If Controller-Target already exist in the Controller table, the existing logic in setOFController
fails badly due to a very basic bug of updating a wrong table.

If the Target exist in the Controller table, the updateRow must happen only on the Bridge Table
and Not on Controller Table. That is the root-cause of the issue seen recently.

While reviewing this bug, I felt that the logic sorrounding this is unncessarily complex and I took
this opportunity to clean it a bit as well.

Change-Id: I14cd38759c16f8b444d2d14bd0b83d1df5a3b45d
Signed-off-by: Madhu Venugopal <mavenugo@gmail.com>
openstack/net-virt-providers/src/main/java/org/opendaylight/ovsdb/openstack/netvirt/providers/openflow13/PipelineOrchestratorImpl.java
plugin/src/main/java/org/opendaylight/ovsdb/plugin/impl/ConfigurationServiceImpl.java