Code Review / ovsdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: f7935c5) | patch
Net-virt is not checking if the master of the net-virt-application is 42/36042/1
authorAnil Vishnoi <vishnoianil@gmail.com>
Mon, 7 Mar 2016 19:00:22 +0000 (11:00 -0800)
committerSam Hague <shague@redhat.com>
Thu, 10 Mar 2016 13:13:06 +0000 (13:13 +0000)
commit7fa749f5040b3bbc16bdd20ec002338c6f920466
treed52eff0406ce69470b4df020ee7fffa812a63663tree | snapshot
parentf7935c5a6be213eefb9bb653a0be8c8fe7fb6ed7commit | diff
Net-virt is not checking if the master of the net-virt-application is
elected at the clustering level or not. Because of this it can end up in a situation
where candidates are registered but owner is not elected and all the instances
gets false when they check for the owner. This patch fixes the issue, where
it waits till owner is selected

Change-Id: I2c720aeac44e4252091952383fe3bb4ed9bed97b
Signed-off-by: Anil Vishnoi <vishnoianil@gmail.com>
openstack/net-virt/src/main/java/org/opendaylight/ovsdb/openstack/netvirt/NetvirtProvider.java diff | blob | history
openstack/net-virt/src/main/java/org/opendaylight/ovsdb/openstack/netvirt/impl/OvsdbInventoryServiceImpl.java diff | blob | history
Open vSwitch Database Management Protocol