[NETCONF-153] mdsal support for testtool Created: 23/Feb/16 Updated: 15/Mar/19 Resolved: 04/Mar/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Behran | Assignee: | Jakub Morvay |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5406 |
| Description |
|
Lithium SR4 test tool still does not support MD-SAL data store (parameter --mdsal). This breaks all Netconf test suites that need testtool (currently all except MDSAL Northbound). |
| Comments |
| Comment by Tomas Cere [ 25/Feb/16 ] |
| Comment by Jozef Behran [ 01/Mar/16 ] |
|
Not fixed yet. Attempt to lock a datastore fails: NetconfDocumentedException{message=RemoteDevice {netconf-test-device}: Lock running failed: [RpcError [message=Unable to lock running datastore, severity=ERROR, errorType=APPLICATION, tag=operation-not-supported, applicationTag=null, info=, cause=null]], errorType=application, errorTag=operation_failed, errorSeverity=warning, errorInfo={}}\n\tat org.opendaylight.controller.sal.connect.netconf.sal.tx.AbstractWriteTx.invokeBlocking(AbstractWriteTx.java:65)\n\tat org.opendaylight.controller.sal.connect.netconf.sal.tx.WriteRunningTx.lock(WriteRunningTx.java:65)\n\t... 64 more\n"}]}} It is also necessary to find and cherry-pick support for Lock and Unlock operations. Otherwise the testtool's MDSAL is unusable with ODL. |
| Comment by Jakub Morvay [ 01/Mar/16 ] |
|
https://git.opendaylight.org/gerrit/#/c/35584/ Problem is, that locking running configuration is not supported operation. However, testtool does not advertise candidate configuration capability and ODL locks running configuration by default. |