[CONTROLLER-1545] Boron RC3.1 Autorelease Build Test Failure: PartitionedCandidateOnStartupElectionScenarioTest Created: 07/Sep/16  Updated: 25/Jul/23  Resolved: 08/Sep/16

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

Type: Bug
Reporter: A H Assignee: Unassigned
Resolution: Done 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: 6659
Priority: Highest

 Description   

Boron RC3.1 is unstable due to a Autorelease Build Test Failure while running
org.opendaylight.controller.cluster.raft.behaviors.PartitionedCandidateOnStartupElectionScenarioTest.runTest:

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/org.opendaylight.controller$sal-akka-raft/244/testReport/junit/org.opendaylight.controller.cluster.raft.behaviors/PartitionedCandidateOnStartupElectionScenarioTest/runTest/

More details can be found below:

Error Message: member 1 behavior state expected:<Leader> but was:<PreLeader>

Stacktrace:
java.lang.AssertionError: member 1 behavior state expected:<Leader> but was:<PreLeader>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.opendaylight.controller.cluster.raft.behaviors.AbstractLeaderElectionScenarioTest.verifyBehaviorState(AbstractLeaderElectionScenarioTest.java:201)
at org.opendaylight.controller.cluster.raft.behaviors.PartitionedCandidateOnStartupElectionScenarioTest.sendElectionTimeoutToFollowerMember1(PartitionedCandidateOnStartupElectionScenarioTest.java:84)
at org.opendaylight.controller.cluster.raft.behaviors.PartitionedCandidateOnStartupElectionScenarioTest.runTest(PartitionedCandidateOnStartupElectionScenarioTest.java:44)

 Comments   
Comment by Tom Pantelis [ 07/Sep/16 ]

Submitted https://git.opendaylight.org/gerrit/#/c/45349/

Comment by A H [ 07/Sep/16 ]

To better assess the impact of this bug and fix, could someone from your team please help us identify the following:
Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Boron without it? Is there a workaround such that we can write a release note and fix in future Boron SR1?
Testing: Could you also elaborate on the testing of this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests?
Impact: Does this fix impact any dependent projects?

Comment by A H [ 07/Sep/16 ]

(In reply to A H from comment #2)
> To better assess the impact of this bug and fix, could someone from your
> team please help us identify the following:

I will reply on behalf of CONTROLLER team.

> Severity: Could you elaborate on the severity of this bug? Is this a
> BLOCKER such that we cannot release Boron without it? Is there a workaround
> such that we can write a release note and fix in future Boron SR1?

Yes, this is a blocker because it causes the autorelease build to be marked as unstable.

> Testing: Could you also elaborate on the testing of this patch? How
> extensively has this patch been tested? Is it covered by any unit tests or
> system tests?

The controller team did not do any additional testing, beyond compile/build/verify in jenkins. The patch will be tested tonight when the next autorelease job runs.

> Impact: Does this fix impact any dependent projects?

No, it does not impact any dependent projects because it is only changes to a test java file, not to any functionality.

Comment by A H [ 08/Sep/16 ]

This fix has been verified as fixed in Boron RC3.2. The build is no longer marked "unstable" and the above mentioned failures no longer appear.

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