+++ This bug was initially created as a clone of Bug #1843042 +++ oc explain configs.spec --api-version=imageregistry.operator.openshift.io/v1 logging <integer> -required- logging determines the level of logging enabled in the registry. Should actually tell me what 0, 1, 2, 3, 4 mean. Otherwise I can't (in console or CLI) actually determine what to set. We should describe the int, the level, and what output it includes. This is an important field, this is a common debug operation, so setting to high. --- Additional comment from Oleg Bulatov on 2020-06-02 22:57:56 CEST --- Note, in 4.6 it's going to be deprecated by logLevel, but it's important to update docs in older releases. Note 2: CRD comes via the image registry operator, so docs needs to be updated, and the update needs to be vendored to cluster-image-registry-operator.
Not much to be done here until we get https://bugzilla.redhat.com/show_bug.cgi?id=1843042 merged and verified.
Depends on the bug 1843042.
Waiting for cherry-pick-approved
Waiting for a newer payload to verify: $ ./oc version Client Version: 4.5.0-0.nightly-2020-09-20-185910 Server Version: 4.5.0-0.nightly-2020-09-18-174934 Kubernetes Version: v1.18.3+b0068a8
$ ./oc version Client Version: 4.5.0-0.nightly-2020-09-20-185910 Server Version: 4.5.0-0.nightly-2020-09-20-185910 Kubernetes Version: v1.18.3+47c0e71 I still can see below display: logging <integer> -required- logging determines the level of logging enabled in the registry. Maybe I verify this bug https://bugzilla.redhat.com/show_bug.cgi?id=1843042#c10 with incorrect steps? since for spec.loglevel, it has description about log level, but also has no such info for spec.logging(it is marked as deprecated now)
Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1843042#c10, I think you have validated it correctly 1. The field "logging" has been deprecated so the message is correct 2. Please check you can see documentation for the field "logLevel", this field is used instead of "logging" from 4.6 onwards As for this one it seems like we missed the bump on the project, I will get it fixed.
Verified on 4.5.0-0.nightly-2020-09-26-194704: logging <integer> -required- logging determines the level of logging enabled in the image registry. Valid values are: 0) log only error messages, 1) log error and warning messages, 2) or 3) log error, warning and information messages, 4) enables debug log.
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.5.14 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-2020:3843