[INTDIST-109] thousands of RFC7950 violation log messages in karaf.log Created: 24/Mar/20  Updated: 30/Sep/20  Resolved: 27/Mar/20

Status: Resolved
Project: integration-distribution
Component/s: None
Affects Version/s: None
Fix Version/s: magnesium

Type: Story Priority: Low
Reporter: Jamo Luhrsen Assignee: Jamo Luhrsen
Resolution: Duplicate Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: Text File openflowplugin_RFC7950_messages.txt    
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
INTDIST-110 clean up RFC7950 violations for netco... Sub-task Resolved Jamo Luhrsen  
INTDIST-111 clean up RFC7950 violations for bgp p... Sub-task Resolved  
INTDIST-112 clean up RFC7950 violations for openf... Sub-task Resolved  
INTDIST-113 clean up RFC7950 violations for aaa p... Sub-task Resolved  
INTDIST-114 clean up RFC7950 violations for ovsdb... Sub-task Resolved  
INTDIST-115 clean up RFC7950 violations for misc ... Sub-task Resolved  

 Description   

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.

 Comments   
Comment by Jamo Luhrsen [ 27/Mar/20 ]

Turns out this is because of yangtools checks being too aggressive and that project
will try to take care of this:

https://jira.opendaylight.org/browse/YANGTOOLS-1090

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