Failing acctest for dependabot MRs

[wilkejo]

Hello @Mongey
I looked into the merge requests from the dependabot and tried to understand why the acctest fails.
I tried it locally as well and had the same issue.

I did some debugging of the test testResourceTopic_produceMessages in which is get often the message Step 1/4 error: Check failed: Check 1/2 error: kafka: Failed to deliver 3 messages.
The debug output states: "ErrNotLeaderForPartition (6)"

I'm not quite sure, maybe this relates to IBM/sarama#2760 ?

Any ideas on that?

[Mongey]

This has stumped me for awhile, it looks like #518 fixes it, with a fix upstream in IBM/sarama#3101

[wilkejo]

That would be nice. I didn't test this.
I think your MR #441 is also related to this?
Maybe this is not needed anymore?

[Mongey]

Yeah, #441 was me attempting to investigate the failures. Seems like #518 may have not fixed it, we've got another failure in main

=== NAME  TestAcc_TopicAlterReplicationFactor
    resource_kafka_topic_test.go:145: Step 1/4 error: Check failed: Check 1/2 error: kafka: Failed to deliver 3 messages.
--- FAIL: TestAcc_TopicAlterReplicationFactor (8.48s)

[wilkejo]

I had a further look into it today but wasn't able to figure out what is happening. I thought maybe Kafka needed some time to sync all changes when the number of partitions changed. I put in a 60 seconds wait but no luck.

One question came to my mind. If I'm not mistaken this is the only place in the test / provider where messages are written to a topic. Why did you include this test there? Is it really required to write messages if the test shall evaluate if the number of partitions has changed?