[CONTROLLER-1489] Cluster bug - RPC returns unexpected response Created: 24/Feb/16  Updated: 19/Oct/17  Resolved: 27/Feb/16

Status: Resolved
Project: controller
Component/s: clustering
Affects Version/s: Beryllium
Fix Version/s: None

Type: Bug
Reporter: Jozef Slezák Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 5417

 Description   

Please fix the error that is periodically appearing in failing Jenkins Job with robot tests:

https://jenkins.opendaylight.org/releng/view/CSIT-3node/job/controller-csit-3node-rest-clust-cars-perf-only-beryllium/12/robot/report/log.html

https://jenkins.opendaylight.org/releng/view/CSIT-3node/job/controller-csit-3node-rest-clust-cars-perf-only-beryllium/1/robot/report/log.html



 Comments   
Comment by Tom Pantelis [ 25/Feb/16 ]

I'm not familiar with these tests. Could you explain a bit what they do? Do they fail every time? Sporadically? Have you investigated whether the issue may be with the tests?

Comment by Tom Pantelis [ 27/Feb/16 ]

The buy-cars RPCs are failing with error code 501:

2016-02-18 21:49:43,503 ERROR: Not all rpc calls passed:

{501: 10000}

It doesn't print the full error but I assume it's due to "No RPC implementation registered".

buy-car is a routed RPC and thus an RPC implementation must be explicitly registered via app code. The clustered-test-app does this via the add-person RPC.

However, in the "Add People" part, the test adds people items via writing to the datastore, as evidenced by the parameters passed to the python script:

python cluster_rest_script.py --port 8181 add --itemtype people --itemcount 10000 --ipr 10000

So the test needs to use the add-person RPC in order to be able to successfully issue buy-car.

The test documentation references https://bugs.opendaylight.org/show_bug.cgi?id=4220 which apparently was opened for this same reason.

Closing this bug as it's not an issue with clustering. Please open a bug in the integration product to address this.

Generated at Wed Feb 07 19:55:41 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.