Bug 1884221
Summary: | IO becomes unhealthy due to a file change | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ricardo Lüders <rluders> |
Component: | Insights Operator | Assignee: | Ricardo Lüders <rluders> |
Status: | CLOSED ERRATA | QA Contact: | Dmitry Misharov <dmisharo> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.6 | CC: | aos-bugs, dmisharo, inecas, tremes |
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
When changing any file that the IO observes, it ended up ending its process in an unclear way.
Consequence:
Undesired ending process signal.
Fix:
Change the error handling for this specific case.
Result:
The IO now doesn't send the ending process signal and keep running.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-24 15:22:14 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
Ricardo Lüders
2020-10-01 11:48:08 UTC
Tested and verified in 4.7.0-0.ci-2020-10-27-064429 Steps to verify: 1. `oc project openshift-insights` 2. Change the content tls.key or tls.crt in openshift-insights-serving-cert secret: `oc edit secret openshift-insights-serving-cert` 3. Wait until insights-operator restarts. 4. `oc describe pod -l app=insights-operator` 5. Containers->insights-operator->Last State->Exit Code is 0 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633 |