Bug 1403169
Summary: | Snapshot : Snapshot restores fails, when nfs ganesha is disable and shared storage is down | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Anil Shah <ashah> | |
Component: | snapshot | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> | |
Status: | CLOSED DEFERRED | QA Contact: | Rahul Hinduja <rhinduja> | |
Severity: | medium | Docs Contact: | ||
Priority: | low | |||
Version: | rhgs-3.2 | CC: | amukherj, atumball, rcyriac, rhinduja, rhs-bugs, storage-qa-internal | |
Target Milestone: | --- | Keywords: | Regression, ZStream | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Known Issue | ||
Doc Text: |
If nfs-ganesha was enabled while taking a snapshot, and during the restore of that snapshot it is disabled or shared storage is down, then the snapshot restore will fail.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1403188 (view as bug list) | Environment: | ||
Last Closed: | 2018-10-11 10:02:28 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, 1403188 |
Description
Anil Shah
2016-12-09 10:45:35 UTC
RCA: Essentially a snapshot of a volume, which was taken when the volume had nfs.ganesha option enabled, has a export.conf file for it. This file will be restored to the Ganesha Export Directory, which has been moved to the shared storage. Currently we fail the snapshot restore in a scenario, where the snapshot has the said conf file, but the shared storage is not available. This behaviour is expected. However there is no option for the user to proceed with the snapshot at this point in time. We will introduce a force option for snapshot restore, which will enable the user to restore this particular snapshot in the above explained scenario, thereby abandoning the export.conf. The reason for introducing the force option is to make the user explicitly ask for the saved export.conf to be abandoned in such a scenario. Since this fix involves introducing CLI change, we propose this to be deferred from 3.2.0 This issue is not considered for releases in last 2 years, RCA available. We are not focusing on fixing the issue in any immediate timeline. Do raise priority on this, if required in any immediate releases! |