-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[ST] Fix StrimziUpgradeST.testUpgradeAcrossVersionsWithUnsupportedKafkaVersion test to run only when there is really an unsupported Kafka version across versions #10496
Conversation
a23110f
to
3cd49a8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. Could you please:
- Fix the DCO signoff? The instructions should be under the
Details
link next to the DCO status in the Pr status section. - Can you please update the PR description? Issues have often a long discussions and in general describe a problem. The PR description should have an explanation what does the PR do and why. Just linking to an issue is not really the same.
systemtest/src/test/java/io/strimzi/systemtest/upgrade/regular/StrimziUpgradeST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/upgrade/regular/StrimziUpgradeST.java
Show resolved
Hide resolved
controllerPods = RollingUpdateUtils.waitTillComponentHasRolledAndPodsReady(TestConstants.CO_NAMESPACE, controllerSelector, 3, controllerPods); | ||
brokerPods = RollingUpdateUtils.waitTillComponentHasRolledAndPodsReady(TestConstants.CO_NAMESPACE, brokerSelector, 3, brokerPods); | ||
eoPods = DeploymentUtils.waitTillDepHasRolled(TestConstants.CO_NAMESPACE, KafkaResources.entityOperatorDeploymentName(clusterName), 1, eoPods); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I expect that this will not work if the Kafka version is unsupported? You have to first change the Kafka version before waiting for a rolling update. Or how does it handle such a situation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I explained what is wrong with the test here: #10495 (comment)
The parsing of Kafka version needs to be fixed, so the test will not be "flaky" and it will test exactly what it should.
In case that this check will be there, it will somehow work now, but when the real unsupported Kafka version will be parsed there, it will fail the test.
@egyedt Any chance to get back to this? Thanks. |
@scholzj |
3cd49a8
to
5ef7836
Compare
d4e5960
to
e3bf6cc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes, they look good to me. Only thing is the removal of this
and final
from the places you are editing in this PR. Could you return them back? I know that there are various code styles that we can use (or you prefer), but we are trying to standardize the final
for the stuff that will not be changed and the this
in the objects classes. Thanks
e3bf6cc
to
ef91327
Compare
@im-konge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great 🙂 thanks a lot for the PR 🚀
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
I checked the failures in the pipeline, but FMPOV they are not relevant to this PR. Maybe @henryZrncik knows more what can be problem here? |
@egyedt because of the logic we have there now, the tests are failing when they are skipped by the assumption -> @henryZrncik is currently working on a fix, once his PR is merged, could you please rebase this PR, so we can run the tests? I will let you know. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@egyedt the PR from @henryZrncik is merged, could you please rebase the PR, so I can trigger the tests? Thanks a lot! |
…only when there is really an unsupported Kafka version across versions Signed-off-by: Egyed Tamas <egyed.t@cloudera.com> Signed-off-by: Tamas Barnabas Egyed <egyed.t@gmail.com>
ef91327
to
4630c73
Compare
Thanks @henryZrncik. |
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
@im-konge It looks like all tests are green now! |
Thanks a lot for the fix @egyedt ! :) |
#10495
Type of change
Description
It is described in #10495.
The problem is that StrimziUpgradeST.testUpgradeAcrossVersionsWithUnsupportedKafkaVersion is use a supported Kafka version from start so the required test with an unsupported Kafka version is not happen. We should use unsupported Kafka version in the test.
Checklist
Please go through this checklist and make sure all applicable tasks have been done