Created attachment 2036927 [details] storageClaim page Description of problem (please be detailed as possible and provide log snippests): Continuing the discussion https://ibm-systems-storage.slack.com/archives/C05RJB6H0LQ/p1715795061549619 about lack of field descriptions, following the bz https://bugzilla.redhat.com/show_bug.cgi?id=2281476 it was decided that StorageClaim - related pages should be removed from the UI. This page was not in the scope for 4.16. Version of all relevant components (if applicable): ODF 4.16.0.120 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? no 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)? 1 Can this issue reproducible? yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Deploy cluster, install ODF Client and open page similar to https://console-openshift-console.apps.ibm-baremetal3.qe.rh-ocs.com/k8s/ns/openshift-storage/operators.coreos.com~v1alpha1~ClusterServiceVersion/ocs-client-operator.v4.16.0-120.stable/ocs.openshift.io~v1alpha1~StorageClaim/~new 2. 3. Actual results: page exists Expected results: page should not exist Additional info:
Changes are required on the operator and not on the UI
Moving the non-blocker BZ out of ODF-4.16.0. If this is a blocker, feel free to propose it as a blocker with justification note.
Please update the RDT flag/text appropriately.
Created attachment 2038163 [details] Storage claim creation page including link
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 (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix update), 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/RHSA-2024:4591