Hi Sanjal Could you please mention in which version is it fixed ? Thanks Mugdha
Hi Mugdha, It should have been fixed for OCP 4.10 & ODF 4.10 Thanks.
Hi **Tested with the following builds :- OCP :- 4.10.0-0.nightly-2022-02-16-171622 ODF :- 4.10.0-156 ** Steps performed for validation of the fix :- (a) Created a user named "mugdha"and project "test". (b) Added admin role to this user of the project. (c) Validated the access of OBC from CLI and Console. ** OBSERVATIONS :- (a) The role "mcg-operator.v4.10.0-noobaa-odf-ui-dc8bf97cd" was automatically created by noobaa. (b) After passing the rolebinding.yaml as mentioned below , the OBC section was present under Storage in UI . [root@localhost mcg-3]# cat RoleBinding.yaml kind: RoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: ui-roles-binding namespace: openshift-storage subjects: - kind: User apiGroup: rbac.authorization.k8s.io # Change this to the user who requires to access OBC page name: tom roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: mcg-operator.v4.10.0-noobaa-odf-ui-dc8bf97cd (c) User was able to create and list OBC in UI under cli as well . Screenshots for the same are present under "https://docs.google.com/document/d/14Eth44WMG3-U4Gggjxbsmict5PDFKlSyKNqFV1Z7J30/edit?usp=sharing" Moving this bug to verified state . Thanks Mugdha
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 (Moderate: OpenShift Container Platform 4.10.3 security 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-2022:0056