Bug 1378342
| Summary: | Getting "NFS Server N/A" entry in the volume status by default. | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Byreddy <bsrirama> | |
| Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | |
| Status: | CLOSED ERRATA | QA Contact: | Byreddy <bsrirama> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.2 | CC: | bsrirama, kaushal, rhinduja, rhs-bugs, storage-qa-internal, vbellur | |
| Target Milestone: | --- | Keywords: | Reopened | |
| Target Release: | RHGS 3.2.0 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8.4-3 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1383005 (view as bug list) | Environment: | ||
| Last Closed: | 2017-03-23 05:48:13 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1351528, 1383005 | |||
|
Description
Byreddy
2016-09-22 08:14:00 UTC
The gluster NFS server has been disabled by default for GlusterFS-3.8 upstream [1]. This is done to encourage users to use NFS-Ganesha for their NFS needs. If RHGS requires this, it can be enabled downstream. [1]: https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8.0.md#glusternfs-disabled-by-default (In reply to Kaushal from comment #2) > The gluster NFS server has been disabled by default for GlusterFS-3.8 > upstream [1]. This is done to encourage users to use NFS-Ganesha for their > NFS needs. > > If RHGS requires this, it can be enabled downstream. > > [1]: > https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8. > 0.md#glusternfs-disabled-by-default Entry should not show by default in the volume status for the first time after volume create and start. This is when we do update from 3.1.3 to 3.2. Have you ensured to bump up the op-version? I don't see this issue when the op-version is bumped up and hence closing this bug. I am reopening this bug based on comment 4 info. For the 3.1.3 volumes we see the "NFS Server N/A" after update to 3.2 + op-version bump up but for the new volumes we create after update we won't see this one. Volume options in the volume info should be same for multiple same volume type by default. (In reply to Byreddy from comment #7) > I am reopening this bug based on comment 4 info. > > For the 3.1.3 volumes we see the "NFS Server N/A" after update to 3.2 + > op-version bump up > but for the new volumes we create after update we won't see this one. > > Byreddy, Apologies! This issue is valid for a 3.2 upgrade path. However what I mentioned in comment 6 is also true but with the patch http://review.gluster.org/#/c/15568/ applied. upstream mainline : http://review.gluster.org/15568 upstream 3.9 : http://review.gluster.org/15652 downstream patch : https://code.engineering.redhat.com/gerrit/#/c/87434 Verified this bug using the build - 3.8.4-3 Fix is working good and i am not seeing the "NFS Server N/A" entry in the volume status after updating 3.1.3 volume to 3.2 available build. Moving to verified state. 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, 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://rhn.redhat.com/errata/RHSA-2017-0486.html |