-
Notifications
You must be signed in to change notification settings - Fork 580
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
CI Failure in controller_upgrade_test.ControllerUpgradeTest.test_updating_cluster_when_executing_operations #5886
Comments
It looks like the errors are being logged while the node is still on v22.1.4. I suspect this is caused by the fact that #5097 seems to only live only on 22.2+, specifically the bits around adding a new exception type for disconnect errors 9ad09f0, d339b68, 07c8b7e To boot, #4895 only lives on 22.1.6+, which likely explains the bare exception. I think I'll go about bumping the version being upgraded from to v22.1.6+, though longer term this is a tricky and annoying problem to solve: the error-log-allow list is itself a sort of loosely defined protocol that evolves over time, but isn't versioned for upgrade tests on dev. Longer term I think we'll probably want to do away with "allowed errors" altogether, but until then there's a fine line between being hiding real bugs and avoiding noise, especially with mixed version tests. |
I agree with @andrwng assessemnt, here's another example I experienced
The log allow list for the test should be extended to include this type of bogus exception. |
Added a commit to update the allow list in https://github.com/redpanda-data/redpanda/pull/5972/commits |
Something similar here. I expected to see the newer named semaphore output, then realized the error may be from the pre-upgrade code. |
Fixes redpanda-data#5886 (cherry picked from commit dacdb3b)
Version & Environment
Redpanda version: dev
https://buildkite.com/redpanda/redpanda/builds/13761#01827bd6-e3be-48dc-8851-3662e1bca36b
What went wrong?
CI Failure
What should have happened instead?
CI Success
How to reproduce the issue?
???
Additional information
And from docker-rp-10, during shutdown:
The text was updated successfully, but these errors were encountered: