-
Story
-
Resolution: Duplicate
-
Low
-
None
-
None
-
None
This can be a top level story and we can open sub tasks for each project that can be used to eventually clean up the yang models to reduce these log messages. They are only coming as
INFO level, but the message itself seems to indicate that their could be a problem.
example:
2020-03-23T10:46:10,403 | INFO | features-3-thread-1 | AbstractListStatementSupport | 499 - org.opendaylight.yangtools.yang-parser-rfc7950 - 4.0.6 | Configuration list (urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?revision=2012-02-06)edit does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [at null:153:4] 2020-03-23T10:46:21,887 | INFO | features-3-thread-1 | AbstractListStatementSupport | 499 - org.opendaylight.yangtools.yang-parser-rfc7950 - 4.0.6 | Configuration list (urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?revision=2012-02-06)edit does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [at [{name=(urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?revision=2012-02-06)ietf-netconf-notifications}]:153:4]
Here's a full karaf.log for reference.
1.
|
clean up RFC7950 violations for netconf project | Resolved | Jamo Luhrsen | |
2.
|
clean up RFC7950 violations for bgp project | Resolved | Unassigned | |
3.
|
clean up RFC7950 violations for openflowplugin project | Resolved | Unassigned | |
4.
|
clean up RFC7950 violations for aaa project | Resolved | Unassigned | |
5.
|
clean up RFC7950 violations for ovsdb project | Resolved | Unassigned | |
6.
|
clean up RFC7950 violations for misc project | Resolved | Unassigned |