When the CSR approver discovers a CSR that it cannot/will not approve, we need to log with proper error level. Right now we're logging with info level and it's confusing. We're also logging innocuous stuff with warning level that should be info level, probably don't need to log at all. Generally need to clean up logging.
@MGugino are you happy to look at this during the next sprint? I would expect a review of the logging for this component shouldn't take too long?
This is blocked my refactor and unit test work. Logging library we want is part of controller runtime package, which we're not using ATM. Once that lands, can update the logging.
Still waiting on the refactor to land
the team is still working to merge the controller-runtime refactor
I'd argue this is more of a feature than a bug, perhaps we should convert this to a Jira task rather than tracking in bugzilla? Either way, we aren't likely to be able to fix this in the 4.7 release so unsetting the target release
I've created https://issues.redhat.com/browse/OCPCLOUD-1105 to track this work instead. We will groom this during backlog grooming and evaluate the importance of this then.