Bug 1948553 - When setting etcd spec.LogLevel is not propagated to etcd operand
Summary: When setting etcd spec.LogLevel is not propagated to etcd operand
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.8.0
Assignee: Lili Cosic
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks: 1954073
TreeView+ depends on / blocked
 
Reported: 2021-04-12 12:35 UTC by Lili Cosic
Modified: 2021-07-27 22:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Spec.LogLevel did not actually set log-level flag on etcd operand. Consequence: Users could not change log level of the etcd operand. Fix: Result: Now when setting the logLevel field in the Spec users can set verbosity of logs for the etcd operand. Log Levels map to etcd as follows: - Debug, Trace and TraceAll map to etcd debug level - Default or Normal log levels map to info log level in etcd
Clone Of:
: 1954073 (view as bug list)
Environment:
Last Closed: 2021-07-27 22:59:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 561 0 None open Bug 1948553: bindata, pkg: Propagate operator log level to etcd itself 2021-04-12 12:37:31 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:59:46 UTC

Description Lili Cosic 2021-04-12 12:35:41 UTC 
Description of problem:

When you set logLevel in the etcd spec.LogLevel the operator does not make use of this value and doesn't set the log level for the etcd operand.


Version-Release number of selected component (if applicable):
4.8


How reproducible:
Every time.


Steps to Reproduce:
1. Set logLevel field in the etcd CustomResource
2. log level for etcd operand does not change

Actual results:


Expected results:


Additional info:
Comment 2 ge liu 2021-04-21 08:15:43 UTC 
Verified with 4.8.0-0.nightly-2021-04-20-195442
Check the etcd cr, the default loglevel is 'Normal', and spec.loglevel in etcd pod is 'info'

# oc edit etcd cluster

Change loglevel to 'Debug', waiting for a couple of minutes, the etcd pods will restart, and verified the spec.loglevel change to 'Debug'
Comment 5 errata-xmlrpc 2021-07-27 22:59:25 UTC 
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.8.2 bug fix and security 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-2021:2438
Note You need to log in before you can comment on or make changes to this bug.