Bug 1879592 - loglevel for the pruner cannot be changed
Summary: loglevel for the pruner cannot be changed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.6.0
Assignee: Oleg Bulatov
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-16 15:12 UTC by Oleg Bulatov
Modified: 2020-10-27 16:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Clone Of:
Environment:
Last Closed: 2020-10-27 16:41:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift api pull 739 0 None closed Bug 1879592: Add logLevel to imagepruners.imageregistry.operator.openshift.io 2020-10-12 20:55:51 UTC
Github openshift cluster-image-registry-operator pull 610 0 None closed Bug 1879592: Bug 1879073: support pruner's spec.logLevel 2020-10-12 20:55:51 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:41:59 UTC

Description Oleg Bulatov 2020-09-16 15:12:36 UTC
Description of problem:

In some cases it is needed to get debug logs from the pruner, but there is no easy way get them.

Comment 3 XiuJuan Wang 2020-09-22 06:03:58 UTC
Verified with 4.6.0-0.nightly-2020-09-21-182309 version.
Could set the pruner to Normal, Debug, Trace and TraceAll methods.
When set to Debug, Trace and TraceAll , the pruner pod log has more details than Normal method.
When set to invalid value, the invalid value will be ingore, and use Normal as default.

Comment 6 errata-xmlrpc 2020-10-27 16:41:47 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.