Bug 2233410 - ROOK_CSI_ENABLE_NFS is not enabled as part of nfs enable from UI
Summary: ROOK_CSI_ENABLE_NFS is not enabled as part of nfs enable from UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.14.0
Assignee: Malay Kumar parida
QA Contact: Amrita Mahapatra
URL:
Whiteboard:
Depends On:
Blocks: 2234664
TreeView+ depends on / blocked
 
Reported: 2023-08-22 07:19 UTC by Amrita Mahapatra
Modified: 2023-11-08 18:55 UTC (History)
2 users (show)

Fixed In Version: 4.14.0-123
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2234664 (view as bug list)
Environment:
Last Closed: 2023-11-08 18:54:15 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-operator pull 2157 0 None open When NFS is enabled on the storagecluster pass ROOK_CSI_ENABLE_NFS: true 2023-08-24 04:49:24 UTC
Github red-hat-storage ocs-operator pull 2164 0 None open Bug 2233410: [release-4.14] When NFS is enabled on the storagecluster pass ROOK_CSI_ENABLE_NFS: true 2023-08-24 19:50:10 UTC
Red Hat Product Errata RHSA-2023:6832 0 None None None 2023-11-08 18:55:04 UTC

Description Amrita Mahapatra 2023-08-22 07:19:24 UTC
Description of problem (please be detailed as possible and provide log
snippests):
From ODF 4.13 an option to enable nfs feature from UI is available while creating a storage cluster.  As part of that it only enables nfs to true in StorageCluster CR now. It should also enable ROOK_CSI_ENABLE_NFS as part of nfs enable from UI.

Version of all relevant components (if applicable):
ODF 4.13

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? Yes we can enable 
ROOK_CSI_ENABLE_NFS flag via patch request,

oc patch cm rook-ceph-operator-config -n openshift-storage -p $'data:\n "ROOK_CSI_ENABLE_NFS":  "true"'

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? yes


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Create an OCP 4.13 cluster and install ODF 4.13
2. Select Enable nfs checkbox while creating the storage cluster
3. Check nfs ganesha pod is up and running but ROOK_CSI_ENABLE_NFS flag is not enabled


Actual results:
ROOK_CSI_ENABLE_NFS is not enabled as part of nfs enabled from UI

Expected results:
It should also enable ROOK_CSI_ENABLE_NFS as part of nfs enable from UI.

Additional info:

Comment 9 Malay Kumar parida 2023-08-31 05:26:35 UTC
Hi Amrita, While checking this I found the build 4.14.0-117 contains changes till the commit before this but not this one. So the fixed in version is wrongly updated actually. You can repeat the test with build 4.14.0-123. I can confirm that one contains the changes.

Another thing is the flag will not be visible in the rook-ceph-operator-config cm. To check the flag do "oc rsh <rook-ceph-opeator-pod-name>"
Then inside that "echo $ROOK_CSI_ENABLE_NFS". This is due to the fact that we are now passing the flag as an env variable to the rook pod from there rook should pick it up. After checking the flag you can check if the nfs system or cr/pod etc. are created.

Comment 12 errata-xmlrpc 2023-11-08 18:54:15 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 (Important: Red Hat OpenShift Data Foundation 4.14.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-2023:6832


Note You need to log in before you can comment on or make changes to this bug.