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

Elasticsearch Invalid phase can only be cleared through downscale #5506

Closed
pebrc opened this issue Mar 22, 2022 · 0 comments · Fixed by #5507
Closed

Elasticsearch Invalid phase can only be cleared through downscale #5506

pebrc opened this issue Mar 22, 2022 · 0 comments · Fixed by #5507
Assignees
Labels
>bug Something isn't working v2.2.0

Comments

@pebrc
Copy link
Collaborator

pebrc commented Mar 22, 2022

} else if !state.IsElasticsearchPhase(esv1.ElasticsearchResourceInvalid) {
// Do not overwrite invalid phase
state.UpdateWithPhase(esv1.ElasticsearchReadyPhase)
}

The above gives special treatment to the invalid phase. That means that once it is set it will never be overwritten unless another non-ready phase is set. But invalid can be a transient state e.g. a license check request that temporary fails or an error in the podTemplate that has been fixed.

if !e.SupportedDistribution {
msg := "Unsupported Elasticsearch distribution"
// unsupported distribution, let's update the phase to "invalid" and stop the reconciliation
d.ReconcileState.
UpdateWithPhase(esv1.ElasticsearchResourceInvalid).

Because we preserve other non-ready phases when we update the phase to ApplyingChanges the only way to clear this status is to scale down the cluster by at least one node or have a node shutdown stall during a rolling upgrade (which is unlikely)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug Something isn't working v2.2.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant