[NETCONF-933] 'commit' sent to devices without 'candidate' capability Created: 16/Dec/22 Updated: 03/Jan/23 Resolved: 03/Jan/23 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | 3.0.8, 4.0.4 |
| Fix Version/s: | 5.0.0, 3.0.9, 4.0.5 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Sangwook Ha | Assignee: | Sangwook Ha |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Configuration of devices without the 'candidate' capability and only with the 'writable-running' capability fails with an 'operation-not-supported' error because a 'commit' RPC is sent to the device which does not support the RPC. For example, this is the error message returned for a PUT request to Calix E9: {
"errors": {
"error": [
{
"error-tag": "operation-not-supported",
"error-info": "TransactionCommitFailedException{message=Netconf transaction commit failed, errorList=[RpcError [message=Netconf transaction commit failed, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=NetconfDocumentedException{message=RPC during tx failed. Unsupported capability :candidate <bad-element>commit</bad-element>, errorType=PROTOCOL, errorTag=operation-not-supported, errorSeverity=ERROR, errorInfo={}}]]}",
"error-message": "RPC during tx failed. Unsupported capability :candidate <bad-element>commit</bad-element>",
"error-type": "protocol"
}
]
}
}
This appears to be a regression of NETCONF-755. |