-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.14, 4.15, 4.16, 4.17
This is a clone of issue OCPBUGS-45236. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-45173. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-45044. The following is the description of the original issue:
—
Description of problem:
The operatorLogLevel reverting back to `Normal` automatically for insightsoperator object
Version-Release number of selected component (if applicable):
4.14,4.15,4.16,4.17
How reproducible:
100%
Steps to Reproduce:
1. Edit the insightsoperator/cluster object: $ oc edit insightsoperator/cluster ... ... spec: logLevel: Normal managementState: Managed operatorLogLevel: Normal ====> Change it to Debug/Trace/TraceAll 2. After 1 Min check if the changes are constant: $ oc get insightsoperator/cluster -o yaml ... ... spec: logLevel: Normal managementState: Managed operatorLogLevel: Normal 3. The OC CLI DOC states that it supports below logLevels: $ oc explain insightsoperator.spec.operatorLogLevel GROUP: operator.openshift.io KIND: InsightsOperator VERSION: v1FIELD: operatorLogLevel <string> ENUM: "" Normal Debug Trace TraceAll DESCRIPTION: operatorLogLevel is an intent based logging for the operator itself. It does not give fine grained control, but it is a simple way to manage coarse grained logging choices that operators have to interpret for themselves. Valid values are: "Normal", "Debug", "Trace", "TraceAll". Defaults to "Normal".
Actual results:
The logLevel is set back to Normal automatically.
Expected results:
The logLevel should not be changed to Normal until manually modified.
Additional info:
The same issue is observed with insightsoperator.spec.logLevel where any logLevel other than Normal getting reverted.
- blocks
-
-
- Closed
-
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- is cloned by
-
-
- Closed
-
- links to
-
RHBA-2024:11502
OpenShift Container Platform 4.16.z bug fix update
[OCPBUGS-46405] [release-4.16] Unable to set the operatorLogLevel to Debug/Trace/TraceAll for insightsoperator object
Verification version
4.16.0-0.nightly-2024-12-17-064130
Verification Type
Automatic-manual
Preparation
Using flexy-install launches an openshift cluster whose image version is 4.16.0-0.nightly-2024-12-17-064130
Verification steps
Run the test case named "test_io_log_level_changed" and verify the result of `test_check_monitor` it.
Expected results
The result of this "test_io_log_level_changed" and "test_check_monitor" are passed
Actual results
The result of this "test_io_log_level_changed" and "test_check_monitor" are passed, and "test_check_monitor" printed it kept monitoring 4465s
tion test_io_log_level_changed didn't find any exception during the monitoring,start time: 1734488560.15421, monitoring time: 4465.0575840473175
Remark
None
baiyang zhou
added a comment - - edited Verification version
4.16.0-0.nightly-2024-12-17-064130
Verification Type
Automatic-manual
Preparation
Using flexy-install launches an openshift cluster whose image version is 4.16.0-0.nightly-2024-12-17-064130
Verification steps
Run the test case named "test_io_log_level_changed" and verify the result of `test_check_monitor` it.
Expected results
The result of this "test_io_log_level_changed" and "test_check_monitor" are passed
Actual results
The result of this "test_io_log_level_changed" and "test_check_monitor" are passed, and "test_check_monitor" printed it kept monitoring 4465s
tion test_io_log_level_changed didn't find any exception during the monitoring,start time: 1734488560.15421, monitoring time: 4465.0575840473175
Remark
None 
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (OpenShift Container Platform 4.16.28 bug fix 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/RHBA-2024:11502