-
Story
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
False
-
False
-
Undefined
-
Originally from https://bugzilla.redhat.com/show_bug.cgi?id=1882500
```
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.
```
DoD:
- Evaluate what logging we are doing throughout the Cluster Machine Approver
- Remove any useless log lines
- Ensure valid/useful logs are being created when a CSR is not approved for some reason
- is related to
-
OCPCLOUD-2017 CMA: Add more info to 'CSR does not appear to be a valid node'
- To Do