https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-1316 netvirt <p>The controller csit tests should be validated to be relevant and applicable.</p> NETVIRT-1316

review existing tests

Sub-task NETVIRT-1315 Medium Resolved Done Victor Pickard Sam Hague csit:3node Tue, 19 Jun 2018 18:53:06 +0000 Wed, 3 Oct 2018 19:36:10 +0000 Wed, 3 Oct 2018 19:35:55 +0000 Fluorine 0 4 <p>this job is probably best to start digging in to next:<br/> <a href="https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/controller%203node/job/controller-csit-3node-clustering-all-oxygen" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/controller%203node/job/controller-csit-3node-clustering-all-oxygen</a></p> <p>Yes, agree. If you look into this job, you will see that these tests:</p> <p> </p> <ol> <li>Start ODL with Tell Based False or True</li> <li>Run some tests</li> <li>Restart ODL with Tell Based True or False</li> <li>Run some more tests</li> </ol> <p> </p> <p>I think the priority would be to focus on issues where ODL is started/restarted with Tell Based False (meaning Ask Based), as my understanding is that Ask Based is what is being currently used by most (if not all) d/s consumers.  So, I'm going to focus on those failures.</p> <p>Controller CSIT 3node clustering oxygen<br/> Failing test cases when Tell Based is False (Ask Based)</p> <p>Job 310 - 0 failures</p> <p>Job 309 - 0 failures</p> <p>Job 308 - 0 failures</p> <p>Job 307 - 2 failures - Partition and Heal</p> <p>Job 306 - 0</p> <p>Job 305 - 1 failure - Chasing the Leader</p> <p>Job 304 - no robot plugin link</p> <p>Job 303 - 4 failures - Global RPC Kill</p> <p>Job 302 - 0</p> <p>Job 301 - 0</p> <p>Job 300 - 0</p> <p>Job 299 - 0</p> <p>Job 298 - 0</p> <p> </p> <p>I've also got a job queued up that I will run with just these tests above. They run just like the normal controller csit, i.e, start/restart odl, run tests, start/restart odl, run tests, repeat.....</p> <p>Should give us a quicker way to run tests and see results (and add debug logs to get quicker results).</p> <p><font color="#333333"><b>Run CSIT with above jobs only as follows:</b></font></p> <p>Restart Odl With Tell Based False</p> <p>Partition and Heal</p> <p>Restart Odl with Tell Based False</p> <p>Chasing the Leader</p> <p>Restart ODL with Tell Based False</p> <p>Global RPC Kill</p> <p>controller/dom_data_broker/restart_odl_with_tell_based_false.robot</p> <p>controller/cluster_singleton/partition_and_heal.robot</p> <p>controller/dom_data_broker/restart_odl_with_tell_based_false.robot</p> <p>controller/cluster_singleton/chasing_the_leader.robot</p> <p>controller/dom_data_broker/restart_odl_with_tell_based_false.robot</p> <p>controller/singleton_service/global_rpc_kill.robot</p> <p> </p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=vpickard" class="user-hover" rel="vpickard">vpickard</a> don't forget the sandbox gets purged at some point on Saturday, every week. All these jobs and logs<br/> are purged. best to keep your job configs in sync with commits in your local (or gerrit patches) releng/builder and<br/> int/test repos, so it's easy to push them back after the purging. Also, if there are some logs you want to keep to look<br/> at later, use the "copy-logs: &lt;job_name&gt;/&lt;job_number&gt;" gerrit keyword (on any patch)</p> Relates NETVIRT-1007 Development Rank 0|i03fp3: