-
Notifications
You must be signed in to change notification settings - Fork 573
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
Unsupported kafka api v3 (leave group) in PartitionMovementUpgradeTest
.test_basic_upgrade
#5868
Comments
Similar failure on the same test, on a different group API FAIL test: PartitionMovementUpgradeTest.test_basic_upgrade (7/37 runs) |
PartitionMovementUpgradeTest
.test_basic_upgrade
When client requests an unsupported API version it is not an unexpected situation and should not be logged with ERROR severity. Introduced separate exception handler for unsupported API version exceptions. Fixes: redpanda-data#5868 Signed-off-by: Michal Maslanka <michal@redpanda.com>
When client requests an unsupported API version it is not an unexpected situation and should not be logged with ERROR severity. Introduced separate exception handler for unsupported API version exceptions. Fixes: redpanda-data#5868 Signed-off-by: Michal Maslanka <michal@redpanda.com>
When client requests an unsupported API version it is not an unexpected situation and should not be logged with ERROR severity. Introduced separate exception handler for unsupported API version exceptions. Fixes: redpanda-data#5868 Signed-off-by: Michal Maslanka <michal@redpanda.com>
This seems similar: https://ci-artifacts.dev.vectorized.cloud/redpanda/018279f4-00b6-44e0-956b-20f174bc3a6e/vbuild/ducktape/results/2022-08-07--001/PartitionMovementUpgradeTest/test_basic_upgrade/138/
|
When client requests an unsupported API version it is not an unexpected situation and should not be logged with ERROR severity. Introduced separate exception handler for unsupported API version exceptions. Fixes: redpanda-data#5868 Signed-off-by: Michal Maslanka <michal@redpanda.com>
Seen again - seems to be the same as the one I reported yesterday: https://buildkite.com/redpanda/redpanda/builds/13844#018281c1-1808-413b-b7e8-9e72e8d0082e
|
@BenPope can you link to the buildkite job (not the artifacts) or the PR? |
@BenPope was that from a 22.1.x run? Perhaps it's just that the fix needs to be backported? |
I guess we are going to keep seeing this unless we backport the change |
Older redpanda versions may not support some of the APIs in versions that the client currently use. Added allowed error log entry to tolerate this situation during an upgrade test. Fixes: redpanda-data#5868 Signed-off-by: Michal Maslanka <michal@redpanda.com>
Older redpanda versions may not support some of the APIs in versions that the client currently use. Added allowed error log entry to tolerate this situation during an upgrade test. Fixes: redpanda-data#5868 Signed-off-by: Michal Maslanka <michal@redpanda.com>
Older redpanda versions may not support some of the APIs in versions that the client currently use. Added allowed error log entry to tolerate this situation during an upgrade test. Fixes: redpanda-data#5868 Signed-off-by: Michal Maslanka <michal@redpanda.com>
Older redpanda versions may not support some of the APIs in versions that the client currently use. Added allowed error log entry to tolerate this situation during an upgrade test. Fixes: redpanda-data#5868 Signed-off-by: Michal Maslanka <michal@redpanda.com>
https://buildkite.com/redpanda/redpanda/builds/13660#01826c94-abff-4f4f-ba8e-e64331d9b328
The text was updated successfully, but these errors were encountered: