Created attachment 2000742 [details] Actual PVC craeyion Page Description of problem: [UI]In Openshift-storage-client namespace, 'RWX' access mode RBD PVC with volumemode'Filesystem' can be created from Client. However, this is an invalid combination for RBD PVC creation From ODF Operator UI of other Platforms. Volume mode is not available when Cepfrbd storageclass and RWX access mode selected on other platform. This is visible in client operator view. This attempt to create PVc and stuck in pending state Version-Release number of selected component (if applicable): How reproducible: 5/5 Steps to Reproduce: 1. Deploy Provider Client setup 2. From UI Create PVC, select storage class : ceph-rbd, RWX access mode, check filemode : in case of this bug 'Filesystem' and 'block' volume mode is visible on UI, select volumemode: Filesystem and create the PVC 3. Actual results: PVC Created and stuck in pending status. PVC event shows error like: Generated from openshift-storage-client.rbd.csi.ceph.com_csi-rbdplugin-provisioner-6d9dcb9fc7-vjj22_2bd4ede5-9418-4c8e-80ae-169b5cb4fa8012 times in the last 13 minutes failed to provision volume with StorageClass "ocs-storagecluster-ceph-rbd": rpc error: code = InvalidArgument desc = multi node access modes are only supported on rbd `block` type volumes Expected results: Volumemode should not be visible on page when PVC with RWX access mode and RBD storage class is selected. Additional info:
Our provisioner names include namespaces, like openshift-storage.rbd.csi.ceph.com. For the client operator, it's in the openshift-storage-client namespace, leading to different provisioner names. This causes the UI to display both Volume modes. In the OCP UI, we've set a fixed mapping for these provisioner names. To fix this, we're considering a few options: Add a New Feature to OCP UI (Only in 4.16): Introduce a new feature in the OCP UI, release the update, and then update the client UI. Change OCS Structure (Only in 4.16, might need more investigation): Modify OCS to remove the namespace from the provisioner namespace. Use JS Tricks in OCP UI (Can be backported to 4.14): Apply some JavaScript tweaks in the OCP UI for partial matching, which could be done more quickly. It's advisable to focus on options 1 and 2 first, considering the issue's severity. Option 3 can be explored later based on urgency and severity.
@skatiyar could you please attach the OCP Console Jira tickets to this BZ.
https://issues.redhat.com/browse/OCPBUGS-25881 for OCP 4.16, once corresponding PR is merged we can backport to earlier versions as well.
adding a 4.16 flag to this BZ for now, but changes are needed on OCP side not on ODF side... once https://issues.redhat.com/browse/OCPBUGS-25881 is Closed will update this BZ with the link to OCP 4.15/4.14 Jira as well !!
(In reply to Sanjal Katiyar from comment #7) > adding a 4.16 flag to this BZ for now, but changes are needed on OCP side > not on ODF side... once https://issues.redhat.com/browse/OCPBUGS-25881 is > Closed will update this BZ with the link to OCP 4.15/4.14 Jira as well !! 4.15 Jira: https://issues.redhat.com//browse/OCPBUGS-28537
@sanjal Katiyar, Could you please share, the "Fixed In Version" details for this BZ fix so that I can verify it ASAP?
Got this comment on my PR: https://github.com/openshift/console/pull/13548#issuecomment-1939510821 (sharing in case it helps). Also, I can see commit being included in the "4.15.0-0.ci-2024-02-12-230304" OCP build (https://amd64.ocp.releases.ci.openshift.org/releasestream/4.15.0-0.ci/release/4.15.0-0.ci-2024-02-12-230304). I haven't verified the same for the "nightly" build, but assuming we have "ci" build, corresponding nightly should have those fixes as well.
(In reply to Sanjal Katiyar from comment #13) > Got this comment on my PR: > https://github.com/openshift/console/pull/13548#issuecomment-1939510821 > (sharing in case it helps). > > Also, I can see commit being included in the "4.15.0-0.ci-2024-02-12-230304" > OCP build > (https://amd64.ocp.releases.ci.openshift.org/releasestream/4.15.0-0.ci/ > release/4.15.0-0.ci-2024-02-12-230304). > I haven't verified the same for the "nightly" build, but assuming we have > "ci" build, corresponding nightly should have those fixes as well. for nightly: Fix included in accepted release 4.15.0-0.nightly-2024-02-12-213938
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.15.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:1383