Skip to content

[8.6][8.7] Investigate failing test ExporterDisableTest.exporterStaysDisabledAfterRestart #37046

@houssain-barouni

Description

@houssain-barouni

,

Description

Slack discussion
ExporterDisableTest.exporterStaysDisabledAfterRestart is frequently failing in stable/8.6 and stable/8.7 PRs and merge queues, there are also flakiness reported in main

Steps to reproduce

In local, the test is consistently failing
https://github.com/camunda/camunda/actions/runs/17067732786/job/48388912890

Current behavior

Error:  io.camunda.zeebe.it.exporter.ExporterDisableTest.exporterStaysDisabledAfterRestart -- Time elapsed: 198.6 s <<< ERROR!
java.util.concurrent.TimeoutException: exporterStaysDisabledAfterRestart() timed out after 120 seconds
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
	Suppressed: org.awaitility.core.ConditionTimeoutException: Condition with alias 'until cluster topology is complete' didn't complete within 3 minutes because assertion condition defined as a Lambda expression in io.camunda.zeebe.qa.util.cluster.TestCluster 
Expecting all elements of:
  [TestStandaloneGateway{nodeId = gateway-0}]
to satisfy given requirements, but these elements did not:

TestStandaloneGateway{nodeId = gateway-0}
error: Expected all partitions to be healthy, but partition <2> of broker <1> is <UNHEALTHY>.
		at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
		at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
		at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
		at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
		at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
		at io.camunda.zeebe.qa.util.cluster.TestCluster.awaitCompleteTopology(TestCluster.java:316)
		at io.camunda.zeebe.qa.util.cluster.TestCluster.awaitCompleteTopology(TestCluster.java:294)
		at io.camunda.zeebe.qa.util.cluster.TestCluster.awaitCompleteTopology(TestCluster.java:280)
		at io.camunda.zeebe.it.exporter.ExporterDisableTest.exporterStaysDisabledAfterRestart(ExporterDisableTest.java:114)
		at java.base/java.lang.reflect.Method.invoke(Method.java:580)
		... 5 more
	Caused by: java.lang.AssertionError: 

Expected behavior

Test to pass

Environment

SM

Version

  • Component Version: [e.g. 2.0.0]

Rootcause

According to the job history, it seems that it started to fail since the merge of #36847, I reverted this PR in my local, and the test is now passing

Solution ideas

No response

Dev -> QA handover

  • Resources:
  • Versions to validate:
  • Release version (in which version this feature will be released):

Links

No response

Metadata

Metadata

Assignees

Labels

affects/8.6Issue is affecting 8.6 minor versionsaffects/8.7Issue is affecting 8.7 minor versionscomponent/zeebeRelated to the Zeebe component/teamkind/bugCategorizes an issue or PR as a bugkind/flakeCategorizes issue or PR as related to a flaky testlikelihood/highA recurring issueseverity/unknownSelect this when determining the severity of a bug issue requires investigationversion:8.6.25version:8.7.11

Type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions