Created attachment 1953726 [details] obc-create-placeholder-absent Created attachment 1953726 [details] obc-create-placeholder-absent Description of problem (please be detailed as possible and provide log snippests): Create OBC via UI, placeholder on StorageClass dropped (see attachment obc-create-placeholder-absent). The placeholder is present in ODF version 4.12. Similar placeholder is present for PVC creation when selecting StorageClass (see attachment pvc-creation-placeholder-analog ) Version of all relevant components (if applicable): OC version: Client Version: 4.12.0-202208031327 Kustomize Version: v4.5.4 Server Version: 4.13.0-0.nightly-2023-03-23-204038 Kubernetes Version: v1.26.2+dc93b13 OCS verison: ocs-operator.v4.13.0-109.stable OpenShift Container Storage 4.13.0-109.stable Succeeded Cluster version NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.0-0.nightly-2023-03-23-204038 True False 159m Cluster version is 4.13.0-0.nightly-2023-03-23-204038 Rook version: rook: v4.13.0-0.8eff918ef2611ffdedd08f9bceeab8b1423bee38 go: go1.19.6 Ceph version: ceph version 17.2.5-75.el9cp (52c8ab07f1bc5423199eeb6ab5714bc30a930955) quincy (stable) 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? no 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? 5/5 Can this issue reproduce from the UI? yes If this is a regression, please provide more details to justify this: The placeholder was present running the test on version: Kubernetes Version: v1.25.7+eab9cc9 cluster channel: stable-4.12 cluster version: 4.12.0-0.nightly-2023-03-15-163541 cluster image: registry.ci.openshift.org/ocp/release@sha256:e1574eee260c2fa2f72e00a82aad0200a99d524dd9fb73afd732d34fa7489227 Steps to Reproduce: 1. Deploy latest ODF 4.13 cluster, log into UI console 2. Navigate to Storage/Object Bucket Claims 3. Click on Create OBC Actual results: placeholder "Select StorageClass" is absent (see attachment obc-create-placeholder-absent) Expected results: placeholder "Select StorageClass" is present Additional info:
Verified: OC version: Client Version: 4.12.0-202208031327 Kustomize Version: v4.5.4 Server Version: 4.13.0-0.nightly-2023-04-15-102029 Kubernetes Version: v1.26.3+19816ee OCS verison: ocs-operator.v4.13.0-164.stable OpenShift Container Storage 4.13.0-164.stable Succeeded Cluster version NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.0-0.nightly-2023-04-15-102029 True False 109m Error while reconciling 4.13.0-0.nightly-2023-04-15-102029: the cluster operator storage is not available Rook version: rook: v4.13.0-0.29c073c4f2fcc059b628779cb763c385a0a8f23c go: go1.19.6 Ceph version: ceph version 17.2.6-10.el9cp (19b8858bfb3d0d1b84ec6f0d3fd7c6148831f7c8) quincy (stable)
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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and 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/RHBA-2023:3742