[NETCONF-540] Missing message-id in error reply when namespace prefix is used Created: 26/Apr/18 Updated: 27/Apr/18 Resolved: 27/Apr/18 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | Oxygen |
| Fix Version/s: | Oxygen |
| Type: | Bug | Priority: | Medium |
| Reporter: | Marek Gradzki | Assignee: | Marek Gradzki |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
I am using Honeycomb with ncclient. Request example <?xml version="1.0" encoding="UTF-8"?> <nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:0a7afdc8-359d-435b-b8cd-9458455b7e5e"> <nc:commit/> </nc:rpc> Reply:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
[...]
</rpc-error>
</rpc-reply>
It is causing troubles for ncclient, because it cannot be matched to request: DEBUG:ncclient.transport.ssh:Broke out of main loop, error=OperationError("Could not find 'message-id' attribute in <rpc-reply>",) DEBUG:ncclient.transport.session:dispatching error to <ncclient.operations.rpc.RPCReplyListener object at 0x7fe7de4b3810> DEBUG:ncclient.transport.session:dispatching error to <ncclient.transport.session.NotificationHandler object at 0x7fe7de4b37d0> INFO:ncclient.operations.rpc:Requesting 'CloseSession' [...] |
| Comments |
| Comment by Marek Gradzki [ 26/Apr/18 ] |
|
master: |
| Comment by Marek Gradzki [ 26/Apr/18 ] |
|
stable/oxygen: |