Fixed a bug in tasks/main, last step "verify the private keys and CSR" #43
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
… to be explictly specified in order to get the key_is_consistent variable in the result
|
I am currently running into this on version 5.1.1. |
zanthorn
approved these changes
Aug 4, 2022
|
This was released in v5.1.2. |
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.
openssl_privatekey_info now requires parameter check_consistency: yes to be explicitly specified in order to get the key_is_consistent variable in the result. Without doing this, openssl_privatekey never sets the "key_is_consistent" variable and the last step of tasks/main,yml fails.
This is on ansible version [core 2.11.7]