-
Notifications
You must be signed in to change notification settings - Fork 15.4k
KAFKA-15378: fix streams upgrade system test #14539
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
Changes from all commits
95f8526
8d5ef8d
677773f
3d9ea7d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -40,11 +40,13 @@ | |
| metadata_1_versions = [str(LATEST_0_10_0)] | ||
| metadata_2_versions = [str(LATEST_0_10_1), str(LATEST_0_10_2), str(LATEST_0_11_0), str(LATEST_1_0), str(LATEST_1_1), | ||
| str(LATEST_2_4), str(LATEST_2_5), str(LATEST_2_6), str(LATEST_2_7), str(LATEST_2_8), | ||
| str(LATEST_3_0)] | ||
| # upgrading from version (2.4...3.0) is broken and only fixed later in 3.1 | ||
| # we cannot test two bounce rolling upgrade because we know it's broken | ||
| # instead we add version 2.4...3.0 to the `metadata_2_versions` upgrade list | ||
| fk_join_versions = [str(LATEST_3_1), str(LATEST_3_2), str(LATEST_3_3)] | ||
| str(LATEST_3_0), str(LATEST_3_1), str(LATEST_3_2), str(LATEST_3_3)] | ||
| # upgrading from version (2.4...3.3) is broken and only fixed later in 3.3.3 (unreleased) and 3.4.0 | ||
| # -> https://issues.apache.org/jira/browse/KAFKA-14646 | ||
| # thus, we cannot test two bounce rolling upgrade because we know it's broken | ||
| # instead we add version 2.4...3.3 to the `metadata_2_versions` upgrade list | ||
| #fk_join_versions = [str(LATEST_3_4)] | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @mimaison You will need to uncomment this, and also add 3.5 release to this list in your PR, and reenable the corresponding
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Noted, I'll do that once this is merged. Thanks |
||
|
|
||
|
|
||
| """ | ||
| After each release one should first check that the released version has been uploaded to | ||
|
|
@@ -202,7 +204,7 @@ def test_upgrade_downgrade_brokers(self, from_version, to_version): | |
| @cluster(num_nodes=6) | ||
| @matrix(from_version=metadata_1_versions, to_version=[str(DEV_VERSION)]) | ||
| @matrix(from_version=metadata_2_versions, to_version=[str(DEV_VERSION)]) | ||
| @matrix(from_version=fk_join_versions, to_version=[str(DEV_VERSION)]) | ||
| #@matrix(from_version=fk_join_versions, to_version=[str(DEV_VERSION)]) | ||
| def test_rolling_upgrade_with_2_bounces(self, from_version, to_version): | ||
| """ | ||
| This test verifies that the cluster successfully upgrades despite changes in the metadata and FK | ||
|
|
||
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.
Log message was changed via fcac880