Details
-
Bug
-
Status: Resolved
-
Resolution: Cannot Reproduce
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
5143
Description
RestPerfClient started with the following command:
java -Xmx1G -XX:MaxPermSize=256M -jar netconf-testtool-1.1.0-20160127.162812-22-rest-perf-client.jar --ip 10.25.2.9 --port 8181 --edits 70 --destination /restconf/config/network-topology:network-topology/topology/topology-netconf/node/17830-sim-device/yang-ext:mount/test:cont --edit-content /home/mininet/TARGET/csit/suites/netconf/restperfclient/../../../variables/netconf/RestPerfClient/request1.json
fails to generate a valid request to ODL. However sending the json directly does work.
The RestPerfClient command comes from the RestPerfClient suite: https://git.opendaylight.org/gerrit/30484
The "send json directly" case is added to the unclustered CRUD suite: https://git.opendaylight.org/gerrit/33756
This was tested on stable/lithium and stable/beryllium. Both are failing. I created tracing logs with the test runs (each log contains the RestPerfClient suite run followed by the patched CRUD suite run) but I can't see any difference between the requests generated by RestPerfClient and those generated by the CRUD suite (maybe the problem is that RestPerfClient does not send any "content-type" HTTP headers? I can't tell as I could not find in the logs what HTTP headers were sent).