Improve the CA not found
error message
#10669
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
When the ZooKeeper or Kafka container starts up, it is trying to find the right CA matching its server certificate to configure the ZooKeeper / Kafka node. When it fails to do so, for example, because the user provided a wrong custom certificates etc., it will print an error
CA not found
and exit.This PR tries to clarify a bit the error message, as we typically have some CAs, but none of them is matching the server certificate. So it tries to be a bit more clear and say that
No CA matching the server certificate found
.Checklist