Bug 1812493
| Summary: | [NooBaa Openshift UI] Some OCS instances are lacking version numbers | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Ben Eli <belimele> | ||||
| Component: | Multi-Cloud Object Gateway | Assignee: | Nimrod Becker <nbecker> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Raz Tamir <ratamir> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.3 | CC: | badhikar, dzaken, ebenahar, etamir, ocs-bugs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-09-17 09:57:32 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: | |||||||
| Attachments: |
|
||||||
Hi Bipul, please update your findings on this issue. Thanks This issue requires changes in the CRD. I observed that the version field is not present in spec of the CRDs supplied by NooBaa. Other interesting thing seen is that in the later OCP releases (4.5 and above) this issue is not applicable as the version field is not shown in the Operand page. @Ben, S33 Bipul's comment. Can you check with OCP 4.5 and above ? 4.6.0-87.ci has no Version column where one exists in the screenshot attached to the BZ. |
Created attachment 1669262 [details] Versions don't show up in the ui Description of problem (please be detailed as possible and provide log snippests): Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: