[CONTROLLER-736] Continuous WARN logs in o.o.y.b.d.c.i.BindingNormalizedNodeCodecRegistry - Path %s does not have a binding equivalent, should have been caught earlier Created: 27/Aug/14 Updated: 27/Aug/14 Resolved: 27/Aug/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Flavio Fernandes | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 1630 | ||||||||
| Description |
|
Ever since the commit below, my log screen is filled with these log messages: https://gist.github.com/55a222333e4805cfc7d8 2014-08-27 08:05:15.929 EDT [DOM-OPER-DCL-989] WARN o.o.y.b.d.c.i.BindingNormalizedNodeCodecRegistry - Path %s does not have a binding equivalent, should have been caught earlier While I believe the intent is to detect an invalid case, there should be a better way to handle it. — commit 47ad12ec82c78d42bb6b0e57991280cb4ee56f4b BUG-650: clarify BindingNormalizedNodeSerializer API contract Non-representable YangInstanceIdentifiers are properly reported via a Also does some implementation house-cleaning geared towards performance, Change-Id: Iea4717c19587fd2cc1e403aae4c5967811240e9a ==== 47ad12ec (Robert Varga 2014-08-26 21:55:22 +0200 132) LOG.warn("Path %s does not have a binding equivalent, should have been caught earl\ |
| Comments |
| Comment by Tony Tkacik [ 27/Aug/14 ] |
|
https://git.opendaylight.org/gerrit/#/c/10363/ This should fix this warnings. |