Fix missing kafka client ca-cert #250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When configuring an appliance as a kafka client the user is asked for the truststore path as well as the ca certificate path from the kafka broker. The truststore is scp'd over but the ca-cert is not causing kafka connections to fail `manageiq-messaging-ready`: ``` manageiq-db.localdomain 9093 - accepting connections ssl.ca.location failed: error:05880002:x509 certificate routines::system lib Kafka is not ready yet ```
|
Checked commit agrare@3288ad8 with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint |
nasark
approved these changes
May 6, 2024
agrare
added a commit
that referenced
this pull request
May 6, 2024
Fixed - Fix missing kafka client ca-cert [#250]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When configuring an appliance as a kafka client the user is asked for the truststore path as well as the ca certificate path from the kafka broker. The truststore is scp'd over but the ca-cert is not causing kafka connections to fail
manageiq-messaging-ready:After manually scp-ing the ca-cert over manageiq-messaging-ready connected successfully and evmserverd started up.