Bug 2208029 - nfs server health is always displaying as "Degraded" under Network file system tab in UI.
Summary: nfs server health is always displaying as "Degraded" under Network file syste...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.13.0
Assignee: Sanjal Katiyar
QA Contact: Amrita Mahapatra
URL:
Whiteboard:
Depends On:
Blocks: 2190241
TreeView+ depends on / blocked
 
Reported: 2023-05-17 17:53 UTC by Amrita Mahapatra
Modified: 2023-08-09 16:46 UTC (History)
4 users (show)

Fixed In Version: 4.13.0-207
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-21 15:25:37 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 852 0 None Merged fix status card for nfs 2023-05-29 06:20:11 UTC
Github red-hat-storage odf-console pull 863 0 None Merged Bug 2208029: [release-4.13] fix status card for nfs 2023-05-29 06:20:12 UTC
Github red-hat-storage odf-console pull 864 0 None Merged Bug 2208029: [release-4.13-compatibility] fix status card for nfs 2023-05-29 06:20:13 UTC
Red Hat Product Errata RHBA-2023:3742 0 None None None 2023-06-21 15:25:48 UTC

Description Amrita Mahapatra 2023-05-17 17:53:50 UTC
Description of problem (please be detailed as possible and provide log
snippests):
Nfs server health is always displaying as "Degraded" with an error sign without any more details under Network file system tab available under “Storage > Data Foundation > Overview when nfs feature is enabled.


Version of all relevant components (if applicable):
OCP: 4.13.0-0.nightly-2023-05-11-225357
ODF: 4.13.0-199


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)? 2


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: No


Steps to Reproduce:
1. Enable nfs feature from CLI using patch command or from UI while creating storagesystem.

oc patch -n openshift-storage storageclusters.ocs.openshift.io ocs-storagecluster --patch '{"spec": {"nfs":{"enable": true}}}' --type merge

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

2. nfs ganesha server is up and running

3. Check StorageSystems --> StorageSystem details dashboad Network file system tab is displayed with nfs server details


Actual results:
Nfs server health is always displaying as "Degraded" with an error sign without any more details under Network file system tab

Expected results:
Appropriate details of nfs server health should be displayed.

Additional info:

Comment 3 Sanjal Katiyar 2023-05-18 07:53:06 UTC
initially it was discussed that a particular metric "worker_threads" will be used to determine the health of the NFS server. But, after discussion with nfs-monitoring team it was noticed that this metric was never part of our product hence never pushed by server as well. So, now we need to update "status" on the dasbboard based on nfs pods health !

Comment 6 Sanjal Katiyar 2023-05-18 16:45:15 UTC
upstream PR: https://github.com/red-hat-storage/odf-console/pull/852

Comment 13 errata-xmlrpc 2023-06-21 15:25:37 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 (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


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