[KAFKA-14905] Failing tests in MM2 ForwardingAdmin test since KIP-894

• Type: Test
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0, 3.4.1, 3.6.0
• Component/s: mirrormaker
• Labels: flaky-test
• Assignee: Greg Harris
• Reporter: Greg Harris
• Created: 13/Apr/23 23:49
• Updated: 21/Apr/23 20:18
• Resolved: 21/Apr/23 20:18

Description

There are three tests which are consistently failing in MirrorConnectorsWithCustomForwardingAdminIntegrationTest since the merge of KIP-894 in KAFKA-14420:

• testReplicationIsCreatingTopicsUsingProvidedForwardingAdmin()
• testCreatePartitionsUseProvidedForwardingAdmin()
• testSyncTopicConfigUseProvidedForwardingAdmin()

org.opentest4j.AssertionFailedError: Condition not met within timeout 60000. Topic: primary.test-topic-1 didn't get created in the FakeLocalMetadataStore ==> expected: <true> but was: <false>
	at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
	at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
	at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
	at app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:211)
	at app//org.apache.kafka.test.TestUtils.lambda$waitForCondition$4(TestUtils.java:337)
	at app//org.apache.kafka.test.TestUtils.retryOnExceptionWithTimeout(TestUtils.java:385)
	at app//org.apache.kafka.test.TestUtils.waitForCondition(TestUtils.java:334)
	at app//org.apache.kafka.test.TestUtils.waitForCondition(TestUtils.java:318)
	at app//org.apache.kafka.test.TestUtils.waitForCondition(TestUtils.java:308)
	at app//org.apache.kafka.connect.mirror.integration.MirrorConnectorsWithCustomForwardingAdminIntegrationTest.waitForTopicToPersistInFakeLocalMetadataStore(MirrorConnectorsWithCustomForwardingAdminIntegrationTest.java:324)
	at app//org.apache.kafka.connect.mirror.integration.MirrorConnectorsWithCustomForwardingAdminIntegrationTest.testReplicationIsCreatingTopicsUsingProvidedForwardingAdmin(MirrorConnectorsWithCustomForwardingAdminIntegrationTest.java:214)
(similar)
	at app//org.apache.kafka.connect.mirror.integration.MirrorConnectorsWithCustomForwardingAdminIntegrationTest.waitForTopicToPersistInFakeLocalMetadataStore(MirrorConnectorsWithCustomForwardingAdminIntegrationTest.java:324)
	at app//org.apache.kafka.connect.mirror.integration.MirrorConnectorsWithCustomForwardingAdminIntegrationTest.testCreatePartitionsUseProvidedForwardingAdmin(MirrorConnectorsWithCustomForwardingAdminIntegrationTest.java:243)
(similar)
	at app//org.apache.kafka.connect.mirror.integration.MirrorConnectorsWithCustomForwardingAdminIntegrationTest.waitForTopicToPersistInFakeLocalMetadataStore(MirrorConnectorsWithCustomForwardingAdminIntegrationTest.java:324)
	at app//org.apache.kafka.connect.mirror.integration.MirrorConnectorsWithCustomForwardingAdminIntegrationTest.testSyncTopicConfigUseProvidedForwardingAdmin(MirrorConnectorsWithCustomForwardingAdminIntegrationTest.java:280)

Issue Links

• relates to: KAFKA-14420 MirrorMaker should not clear filtered configs on target topics
• Testing discovered: KAFKA-14919 MM2 ForwardingAdmin tests should not conflate admin operations
• links to: GitHub Pull Request #13575