Bug 1918920
Summary: | The elasticsearch pods doesn't get restarted automatically after each update | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | KOSAL RAJ I <kiyyappa> | |
Component: | Logging | Assignee: | Gerard Vanloo <gvanloo> | |
Status: | CLOSED NEXTRELEASE | QA Contact: | Anping Li <anli> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 4.5 | CC: | afield, anli, aos-bugs, apjagtap, bleanhar, gvanloo, jkandasa, kearls, mrobson, msweiker, qitang | |
Target Milestone: | --- | |||
Target Release: | 4.8.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | logging-exploration | |||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: The elasticsearch pods are not marked to be restarted after secret changes.
Consequence: The elasticsearch pods doesn't get restarted automatically after each update
Fix: Add a new controller to watch the secret of elasticsearch. If there is any change to the secret, controller will change the elasticsearch cluster's status to be "scheduledRedeploy"
Result: Elasticsearch cluster can be restarted correctly after its secret is changed.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1923788 1952968 (view as bug list) | Environment: | ||
Last Closed: | 2021-07-23 14:50:24 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
KOSAL RAJ I
2021-01-21 17:20:18 UTC
Eric thoughts is this would be fixed by https://github.com/openshift/cluster-logging-operator/pull/858 to fix up the cert storage and generation? It smells of the same issue It seems to be based on the same issue, yes. We have a PR in the works for EO that should help the operator recognize when this happens and reschedule all es pods to be restarted. Hello, As mentioned earlier, this ticket is currently blocking https://issues.redhat.com/browse/TRACING-1725. I moved this issue to urgent as this will now push the customer into an unsupported state, sitting on OCP 4.4. Two jira issues: - 5.1: https://issues.redhat.com/browse/LOG-1205 - 5.0: https://issues.redhat.com/browse/LOG-1206 Closed. This was moved to JIRA: https://issues.redhat.com/browse/LOG-1619 |