https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OVSDB-305 ovsdb <p>The ovsdb.l3.arp.responder.disabled setting is defaulting to disabled. The value in the custom.properties is set to "no" (enabled). But the code in OVSDB is defaulting to yes (disabled).</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-305

ovsdb.l3.arp.responder.disabled is disabled by default, but should be enabled

Bug Resolved Cannot Reproduce Unassigned Sam Hague Fri, 19 Feb 2016 19:01:59 +0000 Thu, 19 Oct 2017 21:26:39 +0000 Wed, 9 Mar 2016 13:30:34 +0000 unspecified openstack.net-virt 0 1 <p>In custom.properties file, we have tried the following cases.<br/> 1. ovsdb.l3.arp.responder.disabled=no then the log shows "Distributed ARP responder is enabled".</p> <p>2016-03-02 17:48:40,202 | DEBUG | config-pusher | DistributedArpService | 280 - org.opendaylight.ovsdb.openstack.net-virt - 1.2.2.SNAPSHOT | Distributed ARP responder is enabled</p> <p>2. ovsdb.l3.arp.responder.disabled=yes then the log shows "Distributed ARP responder is disabled".</p> <p>2016-03-02 18:07:39,005 | DEBUG | config-pusher | DistributedArpService | 280 - org.opendaylight.ovsdb.openstack.net-virt - 1.2.2.SNAPSHOT | Distributed ARP responder is disabled</p> <p>3. ovsdb.l3.arp.responder.disabled is commented then the log shows default value as "Distributed ARP responder is enabled".</p> <p>2016-03-02 18:15:23,503 | DEBUG | config-pusher | DistributedArpService | 280 - org.opendaylight.ovsdb.openstack.net-virt - 1.2.2.SNAPSHOT | Distributed ARP responder is enabled</p> <p>code snippet for above cases,</p> <p> if (configurationService.isDistributedArpDisabled()) </p> { this.flgDistributedARPEnabled = false; LOG.debug("Distributed ARP responder is disabled"); } <p> else </p> { LOG.debug("Distributed ARP responder is enabled"); } <p> By default Distributed ARP responder is enabled.</p> <p>Above cases shows the expected behaviour. Please correct me if I'm wrong.</p> <p>This came up in the opnfv testing, but I think a beryllium rc release was being used.</p> <p>The above scenarios were tested in Beryllium RC release. Please ensures this as an expected behavior thereby we can close this bug else we can proceed further on this bug.</p> Development External issue ID 5393 External issue URL Rank 0|i021wv: