Bug 1379223
| Summary: | "nfs.disable: on" is not showing in Vol info by default for the 3.7.x volumes after updating to 3.9.0 | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Atin Mukherjee <amukherj> | |
| Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | mainline | CC: | bsrirama, bugs, kaushal, rhs-bugs, storage-qa-internal, vbellur | |
| Target Milestone: | --- | Keywords: | Triaged | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.10.0 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1378677 | |||
| : | 1385451 (view as bug list) | Environment: | ||
| Last Closed: | 2017-03-06 17:27:39 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: | 1378677, 1385451 | |||
|
Comment 1
Atin Mukherjee
2016-09-26 05:24:31 UTC
REVIEW: http://review.gluster.org/15568 (glusterd: enable default configurations post upgrade to >= 3.8.0 versions) posted (#1) for review on master by Atin Mukherjee (amukherj) RCA: The options were put up in the dictionary during volume creation and were never recreated during upgrade and hence volume info doesn't show them as default. These options are now been put up in to volume's dictionary when the op-version is bumped up. The volume that was upgraded, will still have gNFS running for it, so volume info not having gNFS is expected and correct. This isn't a bug IMO, and doesn't need anything to be fixed. After a discussion with nfs team, it was agreed upon that 3.9 onwards we will be showing the default options nfs.disable which is 'on' in volume info output for a volume which was configured with older bits i.e. < 3.8.0 REVIEW: http://review.gluster.org/15568 (glusterd: enable default configurations post upgrade to >= 3.9.0 versions) posted (#2) for review on master by Atin Mukherjee (amukherj) (In reply to Atin Mukherjee from comment #1) > Description of problem: > ======================= > The volume option "nfs.disable: on" is not showing for the 3.7.x volumes > after updating to 3.8.x > > Version-Release number of selected component (if applicable): > ============================================================= > This option is showing for the volumes created after updating 3.2. > > > How reproducible: > ================= > Always > > > Steps to Reproduce: > =================== > 1. Have 3.7.x setup with replica-1 volume > 2. Update to 3.8.x > 3. Check volume info > 4. Create a new replica-2 volume > 5. Compare the volume info of replica-1 and replica-2 > > > Actual results: > =============== > "nfs.disable: on" is showing in Vol info by default for the 3.7.x volumes > after updating to 3.8.x > > Expected results: > ================= > Volume options in the volume info should be same for multiple same volume > type by default. We are going to consider this change for a 3.9.x upgrade path not 3.8.x. REVIEW: http://review.gluster.org/15568 (glusterd: enable default configurations post upgrade to >= 3.9.0 versions) posted (#3) for review on master by Atin Mukherjee (amukherj) REVIEW: http://review.gluster.org/15568 (glusterd: enable default configurations post upgrade to >= 3.9.0 versions) posted (#4) for review on master by Atin Mukherjee (amukherj) COMMIT: http://review.gluster.org/15568 committed in master by Kaushal M (kaushal) ------ commit 91c353001c0acf6b6a4c08181fa9a582ae3f880b Author: Atin Mukherjee <amukherj> Date: Sat Sep 24 13:18:24 2016 +0530 glusterd: enable default configurations post upgrade to >= 3.9.0 versions With 3.8.0 onwards volume options like nfs.disable, transport.address-family have some default configuration value. If a volume was created pre upgrade to 3.8.0 or higher the default options are not set post upgrade. This patch takes care of putting the default values in the op-version bump up workflow. However these changes will only reflect from 3.9.0 onwards Change-Id: I9a8d848cd08d87ddcb80dbeac27eaae097d9cbeb BUG: 1379223 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/15568 Reviewed-by: jiffin tony Thottan <jthottan> CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: soumya k <skoduri> Reviewed-by: Kaushal M <kaushal> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report. glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/ |