[OPNFLWPLUG-510] From lithium RC2, when mininet is started before installation of openflowplugin, the node is not updated in operational node datastore Created: 22/Jun/15  Updated: 27/Sep/21  Resolved: 29/Jul/15

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Kalaiselvi Assignee: Kalaiselvi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Text File RC2_karaf.log    
External issue ID: 3829

 Description   

When the mininet is started before the openflowplugin feature is installed in the controller,
the openflowplugin starts, handshakes with the nodes and the nodes are successfully registered to MD-SAL.

But the FlowCapableInventoryProvider of the inventory manager application (in OpenflowPlugin) starts after the openflow handshake with the mininet is completed.
So the node updation notifications provided by the openflowplugin after the handshake completion are missed by the inventory manager application and the nodes are not added to the node datastore.
In these cases, the rest output for the operational node datastore is not populated.

This issue can be reproduced with the standard mininet linear topology itself.



 Comments   
Comment by Kalaiselvi [ 22/Jun/15 ]

Attachment RC2_karaf.log has been added with description: karaf.log

Comment by Michal Rehak [ 22/Jun/15 ]

https://git.opendaylight.org/gerrit/#/c/23074/
merged

Comment by Tomas Cechvala [ 23/Jun/15 ]

worked for me.

Generated at Wed Feb 07 20:32:41 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.