We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue tracker is ONLY used for reporting bugs. Please use the YDK Community for any support issues.
From https://communities.cisco.com/thread/92102
I tried against XRv614 and ydk055 and I see that confirmed commit generate the "persist-id" tag:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:26078be1-3e5f-427f-9058-c953e842054a"> <commit> <persist>1243</persist> <persist-id>1234</persist-id> </commit> </rpc> 2018-06-05 07:07:51,717 - ydk.providers._provider_plugin - DEBUG - <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:26078be1-3e5f-427f-9058-c953e842054a"> <ok/> </rpc-reply>
Tried with XRv641 and still the exact same error as posted above.
But in YKD071 and XRv641 combination the confirmed commit does not generate "persist-id" tag as required per RFC. It generates just the "persist" tag:
2018-06-05 14:58:33,135 - ydk - DEBUG - Trace: Missing message-id in rpc. 2018-06-05 14:58:33,136 - ydk - DEBUG - Netconf SSH Client: sending rpc 2018-06-05 14:58:33,136 - ydk - DEBUG - Trace: Writing message (session 2292223149): <?xml version="1.0"?> <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="3"> <commit> <persist>1234</persist> </commit> </rpc> 2018-06-05 14:58:33,136 - ydk - DEBUG - Netconf SSH Client: receiving rpc 2018-06-05 14:58:33,391 - ydk - DEBUG - Trace: Received message (session 2292223149): <?xml version="1.0"?> <rpc-reply message-id="3" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <rpc-error> <error-type>application</error-type> <error-tag>in-use</error-tag> <error-severity>error</error-severity> <error-message xml:lang="en">'YANG framework' detected the 'fatal' condition 'Datastore locked'</error-message> </rpc-error> </rpc-reply>
Enable logging and post the logs below
The text was updated successfully, but these errors were encountered:
dd0c84c
No branches or pull requests
Issue tracker is ONLY used for reporting bugs. Please use the YDK Community for any support issues.
From https://communities.cisco.com/thread/92102
Expected Behavior
I tried against XRv614 and ydk055 and I see that confirmed commit generate the "persist-id" tag:
Current Behavior
Tried with XRv641 and still the exact same error as posted above.
But in YKD071 and XRv641 combination the confirmed commit does not generate "persist-id" tag as required per RFC. It generates just the "persist" tag:
Steps to Reproduce
Your Script
Logs
Enable logging and post the logs below
System Information
The text was updated successfully, but these errors were encountered: