-
Notifications
You must be signed in to change notification settings - Fork 577
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
Tests: fix upgrade_test #5440
Tests: fix upgrade_test #5440
Conversation
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 addressing this!
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.
LGTM
Upgrade test started failing because older versions of redpanda don't support the partition_autobalancing_mode flag (that was added to default config instead of the deprecated enable_auto_rebalance_on_node_add flag. Looks like the only tests that need a non-default value are node_operations_fuzzy_test (that sets it explicitly) and scaling_up_test (where we explicitly set the value)..
Looks like I missed that |
Sometimes in cithe leader table doesn't get updated in a timely fashion, leading to sporadic partition_balancer_test failures, so looks like the timeout of 30 seconds needs to be increased.
There were also some failures of the new |
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.
Latest changes look good. Just need clean CI run
Failed in e2e_topic_recovery_test (#5241), restarting... |
Cover letter
Upgrade test started failing because older versions of redpanda don't
support the
partition_autobalancing_mode
flag (that was added to the defaultconfig instead of the deprecated
enable_auto_rebalance_on_node_add
flag.Looks like the only tests that need a non-default value are
node_operations_fuzzy_test
(that sets it explicitly anyway) andscaling_up_test
(where we explicitly set the value).Fixes #5437
Release notes