-
Notifications
You must be signed in to change notification settings - Fork 78
Netconf service commit missing "persist-id" tag #796
Copy link
Copy link
Closed
Labels
Description
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:
<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>
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:
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>
Steps to Reproduce
Your Script
Logs
Enable logging and post the logs below
System Information
Reactions are currently unavailable