Bug 1700206
| Summary: | Should use capital letter for the the first word of message "storage backend not configured" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
| Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.1.0 | CC: | aos-bugs |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: the error message `storage backend not configured` is translated to ClusterOperator as is
Consequence: in the web console, the operator's status message starts with a lower-case letter
Fix: add prefix to the error message
Result: the status message starts with an upper-case letter
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-13 17:11:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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 |
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: