Description of problem: Not configure storage for image registry to check the message "storage backend not configured" : $oc describe clusteroperator image-registry Status: Conditions: Last Transition Time: 2019-04-15T05:28:10Z Message: The registry is ready Reason: Ready Status: True Type: Available Last Transition Time: 2019-04-16T05:42:07Z Message: Unable to apply resources: storage backend not configured Reason: Error Status: True Type: Progressing Last Transition Time: 2019-04-16T05:42:07Z Message: storage backend not configured Reason: StorageNotConfigured Status: True Type: Failing Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-04-10-182914 How reproducible: Always Steps to Reproduce: 1.Removed storage config for image-registry 2.Describe clusteroperator image-registry to check warning message 3. Actual results: One message should begin with capital letter: Message: storage backend not configured Expected results: Message: Storage backend not configured Additional info:
Moving low priority 4.x bugs to 4.4.0
Verified on 4.5.0-0.nightly-2020-05-24-223848: Status: Conditions: Last Transition Time: 2020-05-25T09:29:06Z Message: Unable to apply resources: storage backend not configured Reason: Error Status: False Type: Progressing Last Transition Time: 2020-05-25T03:35:43Z Message: The registry is ready Reason: Ready Status: True Type: Available Last Transition Time: 2020-05-25T09:45:20Z Message: Error: storage backend not configured Reason: StorageNotConfigured Status: True Type: Degraded
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, 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:2409