[OVSDB-305] ovsdb.l3.arp.responder.disabled is disabled by default, but should be enabled Created: 19/Feb/16 Updated: 19/Oct/17 Resolved: 09/Mar/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | openstack.net-virt |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Sam Hague | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5393 |
| Description |
|
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). |
| Comments |
| Comment by Karthik Janakaraj [ 03/Mar/16 ] |
|
In custom.properties file, we have tried the following cases. 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 2. ovsdb.l3.arp.responder.disabled=yes then the log shows "Distributed ARP responder is disabled". 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 3. ovsdb.l3.arp.responder.disabled is commented then the log shows default value as "Distributed ARP responder is enabled". 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 code snippet for above cases, if (configurationService.isDistributedArpDisabled()) { this.flgDistributedARPEnabled = false; LOG.debug("Distributed ARP responder is disabled"); }else { LOG.debug("Distributed ARP responder is enabled"); }By default Distributed ARP responder is enabled. Above cases shows the expected behaviour. Please correct me if I'm wrong. |
| Comment by Sam Hague [ 03/Mar/16 ] |
|
This came up in the opnfv testing, but I think a beryllium rc release was being used. |
| Comment by Karthik Janakaraj [ 04/Mar/16 ] |
|
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. |