Bug 1843244
Summary: | [4.5] API documentation for image registry spec.logging field should describe what the logging attributes actually do | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Oleg Bulatov <obulatov> |
Component: | Image Registry | Assignee: | Ricardo Maraschini <rmarasch> |
Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.5 | CC: | aos-bugs, ccoleman, pasik, rmarasch, wzheng |
Target Milestone: | --- | ||
Target Release: | 4.5.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Feature:
Document meaning for "logging" field.
Reason:
It was not documented what each logging level (defined as an integer) mean for the operand.
Result:
Now users can check the documentation to see what each value for this field mean.
|
Story Points: | --- |
Clone Of: | 1843042 | Environment: | |
Last Closed: | 2020-10-12 15:47:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1843042 | ||
Bug Blocks: |
Description
Oleg Bulatov
2020-06-02 20:59:12 UTC
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. Depends on the bug 1843042. 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 |