Skip to content
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

Improve the CA not found error message #10669

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

scholzj
Copy link
Member

@scholzj scholzj commented Oct 2, 2024

Type of change

  • Task

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

  • Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally

@scholzj scholzj added this to the 0.44.0 milestone Oct 2, 2024
@scholzj scholzj changed the title Improve the CA not found message Improve the CA not found error message Oct 2, 2024
@scholzj
Copy link
Member Author

scholzj commented Oct 2, 2024

/azp run zookeeper-regression

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@PaulRMellor PaulRMellor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clear

@scholzj scholzj merged commit f6b2896 into strimzi:main Oct 3, 2024
21 checks passed
@scholzj scholzj deleted the improve-CA-Not-Found-message branch October 3, 2024 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants