Bug 1309209
| Summary: | clone creation with older names in a system fails | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shashank Raj <sraj> | |
| Component: | snapshot | Assignee: | Avra Sengupta <asengupt> | |
| Status: | CLOSED ERRATA | QA Contact: | Anil Shah <ashah> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.1 | CC: | amukherj, asengupt, ashah, asriram, asrivast, mzywusko, nlevinki, rcyriac, rhinduja, rhs-bugs, rjoseph, sankarshan, storage-doc, storage-qa-internal | |
| Target Milestone: | --- | Keywords: | Reopened, ZStream | |
| Target Release: | RHGS 3.3.0 | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8.4-19 | Doc Type: | Bug Fix | |
| Doc Text: |
The names and locations of previously cloned and deleted volumes were not cleaned up correctly. This meant that creating a clone with the same name as a previously deleted clone failed with a 'Commit failed' message. Cleanup is now handled correctly and the same name can be used for a clone in this situation.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1387160 (view as bug list) | Environment: | ||
| Last Closed: | 2017-09-21 04:25:52 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: | 1268895, 1387160, 1417147 | |||
|
Description
Shashank Raj
2016-02-17 08:18:53 UTC
Thanks Laura. It's perfect. The issue is same as 1273722 and will be fixed as part of 1273722 *** This bug has been marked as a duplicate of bug 1273722 *** This has been marked as duplicate by mistake. This needs to be fixed. Patch posted upstream master : http://review.gluster.org/15683 *** Bug 1408386 has been marked as a duplicate of this bug. *** downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101285 [root@rhs-arch-srv1 yum.repos.d]# gluster snapshot clone clone1 snap0 snapshot clone: success: Clone clone1 created successfully [root@rhs-arch-srv1 yum.repos.d]# gluster v list clone1 gluster_shared_storage newvolume vol0 vol1 [root@rhs-arch-srv1 yum.repos.d]# gluster v start clone1 volume start: clone1: success [root@rhs-arch-srv1 yum.repos.d]# gluster v stop clone1 Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y gluster v delete clone1volume stop: clone1: success [root@rhs-arch-srv1 yum.repos.d]# gluster v delete clone1 Deleting volume will erase all information about the volume. Do you want to continue? (y/n) y volume delete: clone1: success [root@rhs-arch-srv1 yum.repos.d]# gluster v list gluster_shared_storage newvolume vol0 vol1 [root@rhs-arch-srv1 yum.repos.d]# gluster snapshot list vol1 snap0_GMT-2017.05.02-06.35.44 snap0 snap1 snap1-2 [root@rhs-arch-srv1 yum.repos.d]# gluster snapshot clone clone1 snap0 snapshot clone: success: Clone clone1 created successfully [root@rhs-arch-srv1 yum.repos.d]# gluster v start clone1 volume start: clone1: success [root@rhs-arch-srv1 yum.repos.d]# Can create clones with same name as previous deleted clone. Bug verified on build glusterfs-3.8.4-24.el7rhgs.x86_64 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://access.redhat.com/errata/RHBA-2017:2774 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://access.redhat.com/errata/RHBA-2017:2774 |