[INTTEST-5] Make clustering scenarios cleanup more thorough Created: 16/May/17  Updated: 19/Oct/17  Resolved: 18/May/17

Status: Resolved
Project: integration-test
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Vratko Polak Assignee: Peter Gubka
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


 Description   

CONTROLLER-1680 and CONTROLLER-1681 already describe situations where a failure from the previous scenario affects the next scenario. The easiest and most reliable cleanup is to use the reboot suite, maybe as a test case in a longer suite.

The recent severe example is this [0] failure, when a leader movement from the previous suite is seen as Candidate state, causing the suite to skip all the relevant checks.

[0] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/686/archives/log.html.gz#s1-s41-t2-k2-k3-k1-k6-k2-k2-k1

 Comments   
Comment by Vratko Polak [ 17/May/17 ]

Another place we need a reboot (aside of Client Isolation and Leader Stability scenarios): Clean leader shutdown [1].

[1] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/692/archives/log.html.gz#s1-s20-t2-k2-k9-k1

Comment by Vratko Polak [ 18/May/17 ]

Fixed with [2].

[2] https://git.opendaylight.org/gerrit/57259

Generated at Wed Feb 07 20:04:18 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.