New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[systemtest][upgrade] Attempt to deflake the upgrade tests and fix sending/receiving messages during upgrade #3546
Conversation
@strimzi-ci run tests test_only profile=upgrade |
❗ Systemtests Failed (no tests results are present) ❗ |
@strimzi-ci run tests test_only profile=upgrade |
...mtest/src/main/java/io/strimzi/systemtest/kafkaclients/internalClients/VerifiableClient.java
Show resolved
Hide resolved
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
✔️ Test Summary ✔️TEST_PROFILE: upgrade |
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Lukas Kral <lukywill16@gmail.com>
Signed-off-by: Lukas Kral <lukywill16@gmail.com>
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
After discussion with @Frawless I'm gonna fix the azure pipelines for upgrade in next PR -> so this can be merge and all issues fixed. |
Signed-off-by: Lukas Kral lukywill16@gmail.com
Type of change
Description
In #3200 I totally forgot that the change of
--broker-list
to--boostrap-server
can affect older versions of Kafka (during the upgrade) -> I tested it only with Kafka 2.5.0 and 2.6.0, problem is that--boostrap-server
option was added to2.5.0
. So I added ternary operator to determine which option use based onKafka
version.Also this is an attempt to deflake the upgrade tests. I assume that main problem of the flakyness was this block of code:
The problem is that if happen that topic is deleted and recreated, the
expectedTopicCount
will be increased and next check will not pass. This assumption is based on given result from PR run:Checklist