DeleteRecordsAuthzIT sometimes fails with a sporadic NOT_LEADER_OR_FOLLOWER #3106
Description
Describe the bug
Following on from #3103
Integration test DeleteRecordsAuthzIT sometimes fails with a sporadic NOT_LEADER_OR_FOLLOWER
mvn verify -Dit.test='DeleteRecordsAuthzIT' -DskipUTs -Dfailsafe.failIfNoSpecifiedTests=false -pl kroxylicious-integration-tests -am
sometimes fails with a:
[ERROR] DeleteRecordsAuthzIT.shouldEnforceAccessToTopics:191->AuthzIT.verifyApiEqivalence:599 [Expect proxied response to be the same as the reference response with equivalent AuthZ] JSON documents are different:
Different value found in node "alice", expected: <"{
"throttleTimeMs" : 0,
"topics" : [ {
"name" : "alice-topic",
"partitions" : [ {
"partitionIndex" : 0,
"lowWatermark" : 0,
"errorCode" : 0
} ]
} ]
}"> but was: <"{
"throttleTimeMs" : 0,
"topics" : [ {
"name" : "alice-topic",
"partitions" : [ {
"partitionIndex" : 0,
"lowWatermark" : -1,
"errorCode" : 6
} ]
} ]
}">.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Running the above command line a loop
- Run command '....'
- See error
Expected behavior
Tests to pass
YAML files and logs
Attach or copy paste your kroxylicious configuration YAML (with sensitive details
like broker address redacted).
Attach or copy and paste relevant logs.
Additional context
Add any other context about the problem here.