Operating System: All
Platform: All

Attachment missing-nodeconnectors-22-Jan-14.txt has been added with description: json output

I am seeing "Ignore edge that contains invalid node connector" log messages that seem to correspond to the missing nodeconnectors (see output below)

2014-01-24 10:23:47.949 GMT [md-sal-binding-commit-7] WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:5:1@MD_SAL|openflow:5->MD_SAL|openflow:6:3@MD_SAL|openflow:6)
2014-01-24 10:23:52.946 GMT [md-sal-binding-commit-4] WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:1:1@MD_SAL|openflow:1->MD_SAL|openflow:2:3@MD_SAL|openflow:2)
2014-01-24 10:23:52.947 GMT [md-sal-binding-commit-7] WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:5:1@MD_SAL|openflow:5->MD_SAL|openflow:6:3@MD_SAL|openflow:6)

This seems to be an adaptor issue:

Output from: "sudo mn --topo=tree,3 --controller=remote,127.0.0.1"

ovsdb-client dump
http://pastebin.com/download.php?i=5yrbq8hn

Warning messages from ODP and switchmanager/default/node/"+nodetype + "/" + nodeid
http://pastebin.com/download.php?i=nDkFsSZ9

output from http://localhost:8080/restconf/datastore/opendaylight-inventory:nodes/node/openflow:5

http://pastebin.com/download.php?i=J4v8gz61

(In reply to Stace Hipperson from comment #1)
> I am seeing "Ignore edge that contains invalid node connector" log messages
> that seem to correspond to the missing nodeconnectors (see output below)
>
> 2014-01-24 10:23:47.949 GMT [md-sal-binding-commit-7] WARN
> o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid
> node connector:
> (MD_SAL|openflow:5:1@MD_SAL|openflow:5->MD_SAL|openflow:6:3@MD_SAL|openflow:
> 6)
> 2014-01-24 10:23:52.946 GMT [md-sal-binding-commit-4] WARN
> o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid
> node connector:
> (MD_SAL|openflow:1:1@MD_SAL|openflow:1->MD_SAL|openflow:2:3@MD_SAL|openflow:
> 2)
> 2014-01-24 10:23:52.947 GMT [md-sal-binding-commit-7] WARN
> o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid
> node connector:
> (MD_SAL|openflow:5:1@MD_SAL|openflow:5->MD_SAL|openflow:6:3@MD_SAL|openflow:
> 6)

I'm using the release artifact for the base edition which I got the following page.

http://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/distributions-base/0.1.0/distributions-base-0.1.0-osgipackage.zip

And, I see the same result with the release artifact.

Any thoughts?

(In reply to Abhijit Kumbhare from comment #4)
> Any thoughts?

It may be already fixed by some patches.
I'll test this with the latest code this weekend.

Thanks Hideyuki! Please let us know what you find - especially Ed.

OVS client dump output

Attachment ovsdb-client dump.txt has been added with description: OVSDB_Client Dump

Tried to reproduce the issue on OF project with following setup:
Mininet version - 2.1.0
OVS version-
ovs-ofctl (Open vSwitch) 2.0.0
Compiled Nov28 2013 01:14:20
OpenFlow versions 0x1:0x4

sudo mn --controller=remote,ip=192.168.56.1 --topo=tree,3 --switch ovsk,protocols=OpenFlow13

Topology view - response from /operational/network-topology:network-topology/topology/flow:1
http://pastebin.com/download.php?i=8K62VurP

Operational Nodes - response from operational/opendaylight-inventory:nodes
http://pastebin.com/download.php?i=bTZJxN5q

Switch Manager Nodes - response from /controller/nb/v2/switchmanager/default/nodes
http://pastebin.com/download.php?i=TWtZUnWS

Also attached the ovsclient dump

Lakshman - so you are not able to reproduce this issue?

I don't see this issues with the latest code.

I pulled the latest code of the Integration Git repository, and built the base edition.
On the base edition, I did the same operation by which I saw the issue on 2014-01-29 (See Comment 3 on the bug report).
But I did not see the issue, and confirmed that I can get all nodeconnectors using the SwitchNorthbound API.
I think this issue has been fixed by a patch which has been merged after Hydrogen release.

[Operation for mininet]
mininet@mininet-vm:~$ mn --version
2.0.0
mininet@mininet-vm:~$ sudo mn --controller=remote,ip=192.168.60.180 --topo tree,3

[Operation for OpenDaylight Controller]

$ git log -1
commit e4ecb6d69d0d7b6b7566fa184386866fb05ae3e1
Author: Robert Varga <rovarga@cisco.com>
Date: Fri Apr 11 17:20:51 2014 +0200

Do not bundle META-INF in configuration

This fixes a packaging issue, where the META-INF directory of
downstream configuration jars would be included in final distribution's
configuration directory – e.g. we had a useless configuration/META-INF
directory.

Should be included in stable branch, too.

Change-Id: I96ad12589876d2585dab5cd3ddee4e271fbb3231
Signed-off-by: Robert Varga <rovarga@cisco.com>

$ ./run.sh -of13

[Operation for SwitchNorthbound API]
I sent GET requests to the following URI.

http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflo
w:1
http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:2
http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:3
http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:4
http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:5
http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:6

Abhijit, This is not reproducible. Shall move it to R with resolution worksforme.