Bug 1878040 - No validation if set invalid value to spec.logLevel and spec.operatorLogLevel in configs.imageregistry.operator.openshift.io
Summary: No validation if set invalid value to spec.logLevel and spec.operatorLogLeve...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.0
Assignee: Ricardo Maraschini
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-11 07:14 UTC by Wenjing Zheng
Modified: 2020-10-27 16:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1883689 1883691 1883692 1883698 1883769 (view as bug list)
Environment:
Last Closed: 2020-10-27 16:40:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift api pull 736 0 None closed Bug 1878040: Validations for LogLevel fields 2021-02-11 15:19:45 UTC
Github openshift api pull 752 0 None closed Bug 1878040: operator: rename etcd CRD to name from repo 2021-02-11 15:19:46 UTC
Github openshift api pull 753 0 None closed Bug 1878040: operator: allow log levels for old clients and unify OperatorLogLevel 2021-02-11 15:19:46 UTC
Github openshift api pull 754 0 None closed Bug 1878040: operator/network: unify defaulting with OperatorSpec log level 2021-02-11 15:19:45 UTC
Github openshift cluster-config-operator pull 158 0 None closed Bug 1878040: Add validation for logLevel 2021-02-11 15:19:45 UTC
Github openshift cluster-csi-snapshot-controller-operator pull 55 0 None closed Bug 1878040: bump(api) to get LogLevel validation 2021-02-11 15:19:46 UTC
Github openshift cluster-csi-snapshot-controller-operator pull 56 0 None closed Bug 1878040: Copy CRD manifest from openshift/api 2021-02-11 15:19:46 UTC
Github openshift cluster-image-registry-operator pull 618 0 None closed Bug 1878040: Add validation for logLevel 2021-02-11 15:19:46 UTC
Github openshift cluster-kube-controller-manager-operator pull 460 0 None closed Bug 1878040: Add validation for logLevel 2021-02-11 15:19:46 UTC
Github openshift cluster-kube-scheduler-operator pull 286 0 None closed Bug 1878040: Add validation for logLevel 2021-02-11 15:19:47 UTC
Github openshift cluster-kube-storage-version-migrator-operator pull 29 0 None closed Bug 1878040: Add validation for logLevel 2021-02-11 15:19:47 UTC
Github openshift cluster-kube-storage-version-migrator-operator pull 30 0 None closed Bug 1878040: operator: allow log levels for old clients and unify OperatorLogLevel 2021-02-11 15:19:47 UTC
Github openshift cluster-openshift-apiserver-operator pull 396 0 None closed Bug 1878040: Add validation for logLevel 2021-02-11 15:19:47 UTC
Github openshift cluster-openshift-controller-manager-operator pull 179 0 None closed Bug 1878040: Add validation for logLevel 2021-02-11 15:19:47 UTC
Github openshift cluster-storage-operator pull 92 0 None closed Bug 1878040: bump(api) to get LogLevel validation 2021-02-11 15:19:47 UTC
Github openshift cluster-storage-operator pull 93 0 None closed Bug 1878040: Copy CRD manifest from openshift/api 2021-02-11 15:19:47 UTC
Github openshift service-ca-operator pull 126 0 None closed Bug 1878040: Add validation for logLevel 2021-02-11 15:19:47 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:40:24 UTC

Description Wenjing Zheng 2020-09-11 07:14:52 UTC
Description of problem:
When set invalid value to spec.logLevel  and spec.operatorLogLevel in configs.imageregistry.operator.openshift.io, no warning appears.

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-09-10-195619

How reproducible:
Always

Steps to Reproduce:
1.Change loglevel and operatorLogLevel with invalid values:
  logLevel: abc
  logging: 0
  managementState: Managed
  observedConfig: null
  operatorLogLevel: abc
2.
3.

Actual results:
No warning appears.

Expected results:
There should be warning appears.

Additional info:

Comment 2 Stefan Schimanski 2020-09-29 08:07:38 UTC
Increasing priority. We should have landed the API change 17 days ago when the controller merged. We have to vendor it into all the operators with logLevels.

Comment 3 Stefan Schimanski 2020-09-29 08:08:01 UTC
Increasing priority. We should have landed the API change 17 days ago when the controller merged. We have to vendor it into all the operators with logLevels.

Comment 6 Wenjing Zheng 2020-10-09 02:32:07 UTC
Verified on 4.6.0-0.nightly-2020-10-08-182439.
configs.imageregistry.operator.openshift.io "cluster" was not valid:
# * spec.operatorLogLevel: Unsupported value: "abc": supported values: "", "Normal", "Debug", "Trace", "TraceAll"

Comment 8 errata-xmlrpc 2020-10-27 16:40:10 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196


Note You need to log in before you can comment on or make changes to this bug.