Issue 465: Fixing tls bad certificate issue #467
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
SrishT
force-pushed
the
issue-465-cert-issue
branch
from
72e7446 to
5fa78ad
Compare
added 4 commits
October 22, 2020 11:39
Signed-off-by: SrishT <[email protected]>
Signed-off-by: SrishT <[email protected]>
Signed-off-by: SrishT <[email protected]>
Signed-off-by: SrishT <[email protected]>
SrishT
force-pushed
the
issue-465-cert-issue
branch
from
5e3cd12 to
c92d967
Compare
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.
Signed-off-by: SrishT [email protected]
Change log description
Pravega Operator logs contain http: TLS handshake error from 172.32.19.2:54178: remote error: tls: bad certificate logs even though a valid certificate has been configured.
Purpose of the change
Fixes #465 and #461
How to verify it
The pravega operator logs should not contain the following error logs after a pravega cluster installation when a valid certificate has been configured
Also when trying to install a pravega cluster version which is unsupported, the installation should fail with an error similar to the one shown below