Bug 1413910
Summary: | Snapshot + NFS : After upgrade from 3.1.3 to 3.2 and restoring snapshot, NFS service is not running | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Anil Shah <ashah> |
Component: | gluster-nfs | Assignee: | Jiffin <jthottan> |
Status: | CLOSED WONTFIX | QA Contact: | Manisha Saini <msaini> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.2 | CC: | amukherj, jthottan, rhinduja, rhs-bugs, skoduri, storage-qa-internal |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
From Red Hat Gluster Storage 3.2 onwards, for every volume the option nfs.disable will be explicitly set to either on or off. The snapshots which were created from 3.1.x or earlier does not have that volume option.
Workaround:
Execute the following command on the volumes:
gluster v set nfs.disable <volname> off
The restored volume will not be exported via gluster nfs.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-07-16 04:52:20 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: | 1351530 |
Description
Anil Shah
2017-01-17 10:06:32 UTC
Given the snap was taken in 3.1.3, nfs.disable option was not touched. Now when this snap is restored, GlusterD didn't bring up the NFS service as nfs.disable is not set to off as per the current code logic. @Jiffin - please confirm if this hypothesis is correct. I think this needs to be marked as a known issue with a work around. Hi jiffin, I have updated the doc text further for the release notes, let me know if this looks ok. Looks good to me |