bad element: interface when calling rpc in nso 5.3.2.3

[atriyant]

I have netconf device (netrounds). My function which invoke rpc from the device, works fine in nso 4.5.3 or .4.7.4.3.

With nso 5.3.2.3 or 5.2.3.3 it get exception below.

It works fine when we triggered from cli, in nso 4 or 5. 

Anyone able to guide where is the issue?

<ERROR> 12-Sep-2020::16:23:08.217 DpActionTrans Did-36-Worker-22: - Exception from action callback
com.tailf.dp.DpCallbackException: com.tailf.maapi.MaapiException: /ncs:devices/device{netrounds}/rpc/rpc-start-test/start-test/parameters/parameter{clients_ipv4}/test-agent-interfaces/test-agent-interface: bad element: interface.

at com.telstra.l3vpnserviceinfo.l3vpnserviceAssurance.startActivation(l3vpnserviceAssurance.java:508) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_232]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_232]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_232]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_232]
at com.tailf.dp.annotations.ActionCallbackProxy.action(ActionCallbackProxy.java:125) ~[conf-api-7.3.2.jar:?]
at com.tailf.dp.DpActionTrans.protoCallback(DpActionTrans.java:316) ~[conf-api-7.3.2.jar:?]
at com.tailf.dp.DpActionTrans.read(DpActionTrans.java:222) [conf-api-7.3.2.jar:?]
at com.tailf.dp.DpActionTrans.run(DpActionTrans.java:129) [conf-api-7.3.2.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_232]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_232]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
at com.tailf.dp.DpThread.run(DpThread.java:42) [conf-api-7.3.2.jar:?]

Thanks.

[atriyant · Accepted solution]

Found out the order of parameters now important. There are four parameters out of many parameters we send to netrounds, now that has to be in order: account, test-agent, interface, ip-version in java with confXMLparam
Peviously the order is just alphabetical: account, interface, ip-version, test-agent
NSO engineers will investigate on why it worked in NSO 4.

Solution: update java code to send the four parameters in order: account, test-agent, interface, ip-version