-
Bug
-
Resolution: Done
-
Medium
-
7.0.0, 7.0.1, 7.0.2
This is caught here :
12:57:57.915 INFO GET Request : url=http://10.30.171.94:8181/rests/data/ietf-yang-library:modules-state path_url=/rests/data/ietf-yang-library:modules-state headers={'User-Agent': 'python-requests/2.31.0', 'Accept-Encoding': 'gzip, deflate', 'Accept': '*/*', 'Connection': 'keep-alive', 'Authorization': 'Basic YWRtaW46YWRtaW4='} body=None 12:57:57.919 INFO GET Response : url=http://10.30.171.94:8181/rests/data/ietf-yang-library:modules-state status=409, reason=Conflict headers={'Set-Cookie': 'JSESSIONID=node01bz4nu9j6qqmt1euu56085c91j0.node0; Path=/rests; HttpOnly, rememberMe=deleteMe; Path=/rests; Max-Age=0; Expires=Sun, 17-Mar-2024 11:57:57 GMT; SameSite=lax', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'Content-Type': 'application/yang-data+json', 'Content-Length': '242'} body={ "errors": { "error": [ { "error-tag": "data-missing", "error-message": "Request could not be completed because the relevant data model content does not exist", "error-type": "protocol" } ] } }
This is related to NETCONF-668, which does not write this state out by default. That implementation also has a few bugs:
- first update may be omitted
- multiple Urls are not supported
- the class is hard to instantiate programmatically
- module names have a weird format with revision appended through _<rev>
All of these should be addressed.
- relates to
-
NETCONF-668 RFC7895/RFC8525 implementation should be independent of any other modules in a separate feature
- Resolved