This repository has been archived by the owner on Mar 30, 2023. It is now read-only.
Fix issue with kibana.keystore and uptaind built-in passwords on cluster start #362
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
This commit updates the kibana keystore operations to use a different command and check for keystore existence location based on version.
This commit updates the built-in password setting process
to check that the security index is green before proceeding.
Due to concurrent password updating from each node, it is possible
for the security index to not be ready when attempting to
update passwords, leading to a response of
{
"error": {
"root_cause": [{
"type": "status_exception",
"reason": "Cluster state has not been recovered yet, cannot write to the [null] index"
}],
"type": "status_exception",
"reason": "Cluster state has not been recovered yet, cannot write to the [null] index"
},
"status": 503
}
russcam
force-pushed
the
fix/cluster-start
branch
from
a59b9ea to
97afa66
Compare
|
tested on 6.8.12, 7.5.2 and 7.9.0. Merging in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR fixes two issues:
{ "error": { "root_cause": [{ "type": "status_exception", "reason": "Cluster state has not been recovered yet, cannot write to the [null] index" }], "type": "status_exception", "reason": "Cluster state has not been recovered yet, cannot write to the [null] index" }, "status": 503 }can be returned when the security index is not ready. This is now handled by waiting for the security index to be green before continuing to update built-in user passwords.
/etc/kibana/kibana.keystore, and requires permissions to create there that the kibana user does not have. For 7.9.0, this PR now checks/etc/kibana/kibana.keystorefor the presence of an existing keystore, and uses root with--allow-rootto interact with the keystore CLI.