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/OPNFLWPLUG-882 OpenFlowPlugin <p>This was done with Carbon</p> <p>Scenario:<br/> 1. Stop ODL<br/> 2. Delete ODL data,journal,snapshots<br/> 3. Delete OF rules on all ovs-switches<br/> 4. Start ODL</p> <p>I can see the device is connected back to ODL, sync rules is starting but it fails.</p> <p>2017-04-18 20:21:38,627 | INFO | entLoopGroup-7-3 | DeviceManagerImpl | 306 - org.opendaylight.openflowplugin.impl - 0.5.0.SNAPSHOT | ConnectionEvent: Device connected to controller, Device:/10.0.77.220:41258, NodeId:Uri <span class="error">&#91;_value=openflow:70825673287310&#93;</span><br/> 2017-04-18 20:21:38,629 | INFO | entLoopGroup-7-2 | DeviceManagerImpl | 306 - org.opendaylight.openflowplugin.impl - 0.5.0.SNAPSHOT | ConnectionEvent: Device connected to controller, Device:/10.0.97.239:56792, NodeId:Uri <span class="error">&#91;_value=openflow:97759666914898&#93;</span><br/> 2017-04-18 20:21:49,517 | INFO | entLoopGroup-7-4 | DeviceManagerImpl | 306 - org.opendaylight.openflowplugin.impl - 0.5.0.SNAPSHOT | ConnectionEvent: Device connected to controller, Device:/10.0.97.239:56794, NodeId:Uri <span class="error">&#91;_value=openflow:97759666914898&#93;</span><br/> 2017-04-18 20:21:49,530 | INFO | entLoopGroup-7-5 | DeviceManagerImpl | 306 - org.opendaylight.openflowplugin.impl - 0.5.0.SNAPSHOT | ConnectionEvent: Device connected to controller, Device:/10.0.77.220:41260, NodeId:Uri <span class="error">&#91;_value=openflow:70825673287310&#93;</span><br/> 2017-04-18 20:21:49,599 | INFO | entLoopGroup-7-6 | DeviceManagerImpl | 306 - org.opendaylight.openflowplugin.impl - 0.5.0.SNAPSHOT | ConnectionEvent: Device connected to controller, Device:/10.0.97.241:46222, NodeId:Uri <span class="error">&#91;_value=openflow:136639621053232&#93;</span><br/> 2017-04-18 20:21:50,008 | INFO | pool-16-thread-1 | DeviceMastership | 341 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.5.0.SNAPSHOT | Triggering reconciliation for device openflow:70825673287310<br/> 2017-04-18 20:21:50,033 | ERROR | on-dispatcher-52 | OutboundQueueProviderImpl | 306 - org.opendaylight.openflowplugin.impl - 0.5.0.SNAPSHOT | No queue present, failing request<br/> 2017-04-18 20:21:50,035 | INFO | on-dispatcher-47 | DeviceMastership | 341 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.5.0.SNAPSHOT | Triggering reconciliation for device openflow:70825673287310<br/> 2017-04-18 20:21:50,043 | INFO | pool-16-thread-1 | DeviceMastership | 341 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.5.0.SNAPSHOT | Triggering reconciliation for device openflow:97759666914898<br/> 2017-04-18 20:21:50,044 | INFO | pool-16-thread-1 | DeviceMastership | 341 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.5.0.SNAPSHOT | Triggering reconciliation for device openflow:136639621053232<br/> 2017-04-18 20:21:50,045 | ERROR | on-dispatcher-52 | OutboundQueueProviderImpl | 306 - org.opendaylight.openflowplugin.impl - 0.5.0.SNAPSHOT | No queue present, failing request<br/> 2017-04-18 20:21:50,054 | INFO | on-dispatcher-47 | DeviceMastership | 341 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.5.0.SNAPSHOT | Triggering reconciliation for device openflow:136639621053232<br/> 2017-04-18 20:21:50,119 | INFO | on-dispatcher-47 | DeviceMastership | 341 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.5.0.SNAPSHOT | Triggering reconciliation for device openflow:97759666914898</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-882

No OF rules after ODL sync

Bug Resolved Cannot Reproduce Unassigned dotans Wed, 19 Apr 2017 10:42:20 +0000 Mon, 27 Sep 2021 09:02:02 +0000 Thu, 4 May 2017 15:43:45 +0000 General 0 2 <p>Attachment karaf-models-dump.tar.gz has been added with description: karaf models (including opendaylght-inventory:nodes)</p> <p>if you remove snapshot and journal and restart the ODL, it's config data store will be empty, so there won't be any flow in config data store. That's the reason you don't see any flow on switch. It's like a clean start up. Please try without step (2), it should work.</p> <p>Please try Anil's suggestion. If still you see some issue - please reopen (if same issue exists) or open another bug (if you find a different issue).</p> Development External issue ID 8245 External issue URL Rank 0|i033w7: