[SNMP4SDN-13] snmp4sdn features failing to resolve features in Beryllium Created: 04/Dec/15  Updated: 19/Oct/17  Resolved: 16/Feb/16

Status: Verified
Project: snmp4sdn
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Thanh Ha (zxiiro) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 4720

 Description   

[WARNING] The POM for org.opendaylight.controller:features-adsal:xml:features:0.10.0-Daily-v201512031659 is missing, no dependency information available

[WARNING] The POM for org.opendaylight.controller:features-nsf:xml:features:0.6.0-Daily-v201512031659 is missing, no dependency information available



 Comments   
Comment by Thanh Ha (zxiiro) [ 04/Dec/15 ]

Proposed patch: https://git.opendaylight.org/gerrit/30692/

Comment by Thanh Ha (zxiiro) [ 07/Dec/15 ]

Discussion on this topic can be found on this thread:

https://lists.opendaylight.org/pipermail/release/2015-December/004807.html

We've also temporarily disabled snmp4sdn from integration and autorelease until this issue is resolved.

Comment by Stephen Kitt [ 04/Jan/16 ]

The fix has now been merged.

Comment by Vratko Polak [ 04/Jan/16 ]

The fix is not good enough for integration/distribution, as it leads to "Address already in use" BindException in runtime, presumably due to an old AD-SAL based OpenFlow implementation (or something similar) being pulled in.

For more info see comments in https://git.opendaylight.org/gerrit/#/c/30272

Ideally, snmp4sdn should use OpenFlow related features from OpenFlowPlugin project of the same cycle (currently Beryllium snapshot).

Comment by Stephen Kitt [ 04/Jan/16 ]

Vratko, I'd say that's a different bug... (The features resolve but can't initialise properly.)

I've also tried plugging in SingleFeatureTest on snmp4sdn and that breaks in all sorts of ways too.

Comment by A H [ 04/Feb/16 ]

Vratko, do we know if this still causes an "Address already in use" BindException in runtime, or has this been fixed as well?

Comment by Christine Hsieh [ 16/Feb/16 ]

Aforementioned two bugs and the patch is merged, close this bug report.
https://git.opendaylight.org/gerrit/#/c/30272
1. feature install fail: fixed
2."Address already in use" BindException: does not appear in latest successful build

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