[CONTROLLER-811] Installing ODL-RESTCONF feature causes missing yang file exception Created: 11/Sep/14 Updated: 11/Nov/14 Resolved: 11/Nov/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Devin Avery | Assignee: | Devin Avery |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| External issue ID: | 1819 |
| Description |
|
It appears that the order of bundles in the feature.xml matters in terms of how the yang files are loaded by the config subsystem. When I do a feature:install odl-restconf I see the below exception: 2014-09-11 12:34:29,218 | INFO | Local user karaf | SharedSchemaContextFactory | 96 - org.opendaylight.yangtools.yang-parser-impl - 0.6.2.SNAPSHOT | Failed to assemble sources == Full Exception @ end === When I modify the odl-restconf feature and move the <bundle>mvn:org.opendaylight.controller/sal-remote/${mdsal.version}</bundle> above <bundle>mvn:org.opendaylight.controller/sal-rest-connector/${mdsal.version}</bundle> the exception goes away. Unknown what affects this have. ==== Possible Resolution ==== Move the bundle for now, and long term we should look at removing the order dependency. ==== FULL EXCEPTION ==== 2014-09-11 12:34:29,218 | INFO | Local user karaf | SharedSchemaContextFactory | 96 - org.opendaylight.yangtools.yang-parser-impl - 0.6.2.SNAPSHOT | Failed to assemble sources |
| Comments |
| Comment by Devin Avery [ 11/Sep/14 ] |
|
Change for temporary fix is in https://git.opendaylight.org/gerrit/11062 Created |
| Comment by Tony Tkacik [ 12/Sep/14 ] |
|
Thrown exception is innocent, MD-SAL only detected incorrect start order report and will reattemt to parse models after another bundle started. Model will be parsed once all its dependencies are satisfied. See https://bugs.opendaylight.org/show_bug.cgi?id=1774 for more details about this error report. |