[NETCONF-725] ietf-yang-library version conflict Created: 15/Sep/20 Updated: 14/May/21 Resolved: 13/May/21 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | Aluminium |
| Fix Version/s: | Aluminium SR4, 1.13.2 |
| Type: | Bug | Priority: | High |
| Reporter: | Valentin Mayamsin | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
Freshly installed nightly build of aluminum. feature:install odl-restconf-nb-rfc8040. There are two versions of ietf-yang-library deployed: org.opendaylight.mdsal.binding.model.ietf:rfc7895:jar:6.0.4 org.opendaylight.mdsal.binding.model.ietf:rfc8525:jar:6.0.4 This leads to query conflict: $ curl -u admin:admin -X GET http://localhost:8181/rests/yang-library-version {"ietf-restconf:yang-library-version":"2016-06-21"} $ curl -u admin:admin -X GET http://localhost:8181/rests/data/ietf-yang-library:modules-state?content=nonconfig 11:24:11.812 TRACE [qtp323653443-77] Tx member-1-datastore-operational-fe-3-txn-2-0 read /(urn:ietf:params:xml:ns:yang:ietf-yang-library?revision=2019-01-04)modules-state
{"errors":{"error":[{"error-tag":"data-missing","error-type":"protocol","error-message":"Request could not be completed because the relevant data model content does not exist"}]}}
However if all data is requested, it finally returns ietf-yang-library:modules-state:
$ curl -u admin:admin -X GET http://localhost:8181/rests/data/
... etf:params:restconf:capability:fields:1.0","urn:ietf:params:restconf:capability:filter:1.0","urn:ietf:params:restconf:capability:replay:1.0" ,"urn:ietf:params:restconf:capability:with-defaults:1.0"]}},"ietf-yang-library:modules-state":{"module":[ {"name":"aaa","revision":"2016-12-14","namespace":"urn:opendaylight:params:xml:ns:yang:aaa","confo rmance-type":"import","schema":"/modules/aaa/2016-12-14"},{"name":"aaa-app-config","revision":"2017-06-19","namespace":"urn:opendaylight:aaa:app:config","conformance-type":"import","schema":"/modules/aaa -app-config/2017-06-19"},{"name":"aaa-cert","revision":"2015-11-26","namespace":"urn:opendaylight:yang:aaa:cert","conformance-type":"import","schema":"/modules/aaa-cert/2015-11-26"},{"name":"aaa-cert-mds al","revision":"2016-03-21","namespace":"urn:opendaylight:yang:aaa:cert
... { "name":"ietf-yang-library", "revision":"2019-01-04", "namespace":"urn:ietf:params:xml:ns:yang:ietf-yang-library", "conformance-type":"import", "schema":"/modules/ietf-yang-library/2019-01-04" } , { "name":"ietf-yang-library", "revision":"2016-06-21", "namespace":"urn:ietf:params:xml:ns:yang:ietf-yang-library", "conformance-type":"import", "schema":"/modules/ietf-yang-library/2016-06-21" }, ... |
| Comments |
| Comment by Robert Varga [ 14/Oct/20 ] |
|
It looks like there are multiple culprits here. sal-netconf-connector is using the down-revved model, as is restconf-common. |