-
Notifications
You must be signed in to change notification settings - Fork 592
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 (key symptom) in RandomNodeOperationsTest.test_node_operations
#17739
Labels
auto-triaged
used to know which issues have been opened from a CI job
ci-failure
team/enterprise
helper for jira sync
Comments
vbotbuildovich
added
auto-triaged
used to know which issues have been opened from a CI job
ci-failure
labels
Apr 10, 2024
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Apr 26, 2024
Previously the service_unavailable error code was mapped to generic unexpected server error. This lead to a situation in which a lot of errors were logged when broker was restarted as it has an RPC server running but without the services registered. Changed the mapping of `rpc::errc::service_unavailable` to HTTP service unavailable error. Fixes: redpanda-data#17739 Signed-off-by: Michał Maślanka <michal@redpanda.com>
7 tasks
vbotbuildovich
pushed a commit
to vbotbuildovich/redpanda
that referenced
this issue
Apr 26, 2024
Previously the service_unavailable error code was mapped to generic unexpected server error. This lead to a situation in which a lot of errors were logged when broker was restarted as it has an RPC server running but without the services registered. Changed the mapping of `rpc::errc::service_unavailable` to HTTP service unavailable error. Fixes: redpanda-data#17739 Signed-off-by: Michał Maślanka <michal@redpanda.com> (cherry picked from commit 1a9f248)
vbotbuildovich
pushed a commit
to vbotbuildovich/redpanda
that referenced
this issue
Apr 26, 2024
Previously the service_unavailable error code was mapped to generic unexpected server error. This lead to a situation in which a lot of errors were logged when broker was restarted as it has an RPC server running but without the services registered. Changed the mapping of `rpc::errc::service_unavailable` to HTTP service unavailable error. Fixes: redpanda-data#17739 Signed-off-by: Michał Maślanka <michal@redpanda.com> (cherry picked from commit 1a9f248)
This was referenced Apr 26, 2024
mmaslankaprv
added a commit
to vbotbuildovich/redpanda
that referenced
this issue
Apr 30, 2024
Previously the service_unavailable error code was mapped to generic unexpected server error. This lead to a situation in which a lot of errors were logged when broker was restarted as it has an RPC server running but without the services registered. Changed the mapping of `rpc::errc::service_unavailable` to HTTP service unavailable error. Fixes: redpanda-data#17739 Signed-off-by: Michał Maślanka <michal@redpanda.com> (cherry picked from commit 1a9f248)
mmaslankaprv
added a commit
to vbotbuildovich/redpanda
that referenced
this issue
Apr 30, 2024
Previously the service_unavailable error code was mapped to generic unexpected server error. This lead to a situation in which a lot of errors were logged when broker was restarted as it has an RPC server running but without the services registered. Changed the mapping of `rpc::errc::service_unavailable` to HTTP service unavailable error. Fixes: redpanda-data#17739 Signed-off-by: Michał Maślanka <michal@redpanda.com> (cherry picked from commit 1a9f248)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-triaged
used to know which issues have been opened from a CI job
ci-failure
team/enterprise
helper for jira sync
https://buildkite.com/redpanda/vtools/builds/12756
JIRA Link: CORE-2220
The text was updated successfully, but these errors were encountered: