Description of problem: The log level for the image registry operator is static and set at a relatively high level (0). This cannot be changed without using a CVO override [1] or scaling the CVO deployment to 0. Version-Release number of selected component (if applicable): 4.1.0 How reproducible: Always Steps to Reproduce: 1. Increase the log Level of the image registry operator config to 5 (i.e. debug) 2. Tail the logs of the cluster image registry operator Actual results: Only high level info logs, warnings, and errors are logged Expected results: Debug messages are logged. Additional info: [1] https://github.com/openshift/cluster-version-operator/blob/master/docs/dev/clusterversion.md#setting-objects-unmanaged
After some discussions we have decided to move this to the next version. We have been living with this behavior for a while and to introduce a fix for it in 4.5 involve risks we are not willing to take so close to code freeze. This one requires changes on openshift/api as well as in image registry operator, we have to be careful with how we gonna tackle backward compatibility and that increases the risk.
Fix for this one is awaiting for review/approval.
QE can see image registry to debug log level on 4.6.0-0.nightly-2020-09-10-195619.
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