Bug 2188667

Summary: [Backport to 4.12.3][Fusion-aaS]wrong label in new storageclassrequest cr
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Subham Rai <srai>
Component: ocs-operatorAssignee: Subham Rai <srai>
Status: CLOSED ERRATA QA Contact: Elena Bondarenko <ebondare>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.12CC: ebenahar, nberry, nigoyal, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ODF 4.12.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2188666 Environment:
Last Closed: 2023-05-23 09:17:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2188666    
Bug Blocks:    

Description Subham Rai 2023-04-21 14:45:39 UTC
+++ This bug was initially created as a clone of Bug #2188666 +++

Description of problem (please be detailed as possible and provide log
snippests):

Wrong label applied on newly storageclassrequest cr.
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:

--- Additional comment from RHEL Program Management on 2023-04-21 14:43:16 UTC ---

This bug having no release flag set previously, is now set with release flag 'odf‑4.13.0' to '?', and so is being proposed to be fixed at the ODF 4.13.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.

--- Additional comment from Subham Rai on 2023-04-21 14:43:41 UTC ---

https://github.com/red-hat-storage/ocs-operator/pull/1913/files#r1173637973

Comment 8 Elena Bondarenko 2023-05-03 14:15:27 UTC
I tested with ocs-operator.v4.12.3-rhodf (upgraded cluster).
oc get clusterrole storageclassrequests.ocs.openshift.io-v1alpha1-admin -A -oyaml|grep -A 5 -B 5 storageclassrequests output includes
rules:
- apiGroups:
  - ocs.openshift.io
  resources:
  - storageclassrequests
  verbs:
  - '*'

Comment 14 errata-xmlrpc 2023-05-23 09:17:41 UTC
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: Red Hat OpenShift Data Foundation 4.12.3 Security 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/RHSA-2023:3265