[L2SWITCH-41] Inventory details for host getting populated incorrectly Created: 16/Apr/15  Updated: 19/Oct/17  Resolved: 24/Feb/16

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

Type: Bug
Reporter: Priyanka Chopra Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All


Attachments: Text File network-topology-operational.txt     Text File opendaylight-inventory-operational.txt    
External issue ID: 3003

 Description   

I pulled the latest code of L2switch from github and connected mininet (linear
topology for 2 switches).
Topology details:
h1-eth1(10.0.0.1) --> s1-eth1
s1-eth2 --> s2-eth2
s2-eth1 --> h2-eth1(10.0.0.2)

When I retrieved data using the API :-- http://<controller IP>:8181/restconf/config/opendaylight-inventory:nodes

The node-connector details have invalid enteries.
It displays 2 enteries for each host ie -
h1-eth1 attached to s1-eth1
h2-eth1 attached to s1-eth2

similarly
h2-eth1 attached to s2-eth1
h1-eth1 attached to s2-eth2



 Comments   
Comment by Colin Dixon [ 19/Jan/16 ]

We should see if we can reproduce this.

Comment by Ajay L [ 16/Feb/16 ]

Attachment network-topology-operational.txt has been added with description: Network topology output as expected

Comment by Ajay L [ 16/Feb/16 ]

Attachment opendaylight-inventory-operational.txt has been added with description: Inventory output as expected

Comment by Ajay L [ 16/Feb/16 ]

Tested this scenario on Helium-SR4 and Beryllium-RC2.3

Firstly the data is available on operational and not config as mentioned in the bug description

I am getting expected output from host and address tracking. Output attached for reference

Please try the test again and see if you can repro. Attach the config/operational GET output for inventory & topology data

Comment by Ajay L [ 24/Feb/16 ]

Tested on He and Be and works fine for me. Please re-open the bug if issue is seen again

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