Back to bug 1309209

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-02-17 08:18:56 UTC Keywords ZStream
Avra Sengupta 2016-02-17 08:37:05 UTC Blocks 1268895
Avra Sengupta 2016-02-17 08:41:27 UTC Doc Text Brick paths of a cloned volume, which are present under /run/gluster/snaps/ are not cleaned up when the cloned volume is deleted. Not cleaning these brick entries in /run/gluster/snaps/ will lead to failure in creation of new cloned volumes with the same name.
Doc Type Bug Fix Known Issue
Avra Sengupta 2016-02-17 09:54:41 UTC Doc Text Brick paths of a cloned volume, which are present under /run/gluster/snaps/ are not cleaned up when the cloned volume is deleted. Not cleaning these brick entries in /run/gluster/snaps/ will lead to failure in creation of new cloned volumes with the same name. Brick paths of a cloned volume, which are present under /run/gluster/snaps/ are not cleaned up when the cloned volume is deleted. After a cloned volume is deleted, the brick entries in /run/gluster/snaps/ should be unmounted, deleted, and their respective brick lvs removed. Failing to do so, will lead to failure in creation of new cloned volumes with the same name.
Laura Bailey 2016-02-19 03:06:59 UTC Doc Text Brick paths of a cloned volume, which are present under /run/gluster/snaps/ are not cleaned up when the cloned volume is deleted. After a cloned volume is deleted, the brick entries in /run/gluster/snaps/ should be unmounted, deleted, and their respective brick lvs removed. Failing to do so, will lead to failure in creation of new cloned volumes with the same name. When a cloned volume is deleted, its brick paths (stored under /run/gluster/snaps) are not cleaned up correctly. This means that attempting to create a clone that has the same name as a previously cloned and deleted volume fails with a Commit failed message.

Workaround:
After deleting a cloned volume, ensure that brick entries in /run/gluster/snaps are unmounted and deleted, and that their logical volumes are removed.
Flags needinfo?(asengupt)
Avra Sengupta 2016-02-19 08:04:56 UTC Flags needinfo?(asengupt)
Anjana Suparna Sriram 2016-03-08 12:22:29 UTC Keywords Documentation
Anjana Suparna Sriram 2016-03-08 13:05:17 UTC Blocks 1310215
Rahul Hinduja 2016-03-17 06:37:57 UTC CC rhinduja
Component Documentation gluster-snapshot
Blocks 1310215
Assignee storage-doc rjoseph
Rahul Hinduja 2016-03-17 06:39:11 UTC Summary Add documentation for clone creation with older names in a system. clone creation with older names in a system fails
Rejy M Cyriac 2016-03-17 07:05:03 UTC Keywords Documentation
CC rcyriac
Avra Sengupta 2016-07-14 09:21:51 UTC Status NEW CLOSED
Resolution --- DUPLICATE
Last Closed 2016-07-14 05:21:51 UTC
Rejy M Cyriac 2016-09-17 12:54:11 UTC CC storage-qa-internal
Component gluster-snapshot snapshot
Avra Sengupta 2016-10-18 06:21:19 UTC Status CLOSED NEW
Resolution DUPLICATE ---
Keywords Reopened
Avra Sengupta 2016-10-18 06:22:49 UTC Status NEW ASSIGNED
Assignee rjoseph asengupt
Avra Sengupta 2016-10-20 09:24:36 UTC Blocks 1387160
Avra Sengupta 2016-10-20 09:32:04 UTC Status ASSIGNED POST
John Skeoch 2016-11-08 03:54:34 UTC CC sashinde
John Skeoch 2016-11-18 04:11:26 UTC CC sashinde mzywusko
Avra Sengupta 2016-12-23 09:41:38 UTC CC ashah
Avra Sengupta 2017-02-21 10:20:24 UTC CC rjoseph
Blocks 1417147
Atin Mukherjee 2017-02-21 10:57:32 UTC CC amukherj
Alok 2017-02-28 06:27:25 UTC CC asrivast
Red Hat Bugzilla Rules Engine 2017-03-06 13:12:37 UTC Target Release --- RHGS 3.3.0
Atin Mukherjee 2017-03-24 08:43:33 UTC Status POST MODIFIED
errata-xmlrpc 2017-03-30 21:16:13 UTC Status MODIFIED ON_QA
Milind Changire 2017-03-30 21:45:16 UTC Fixed In Version glusterfs-3.8.4-19
Rahul Hinduja 2017-04-03 07:38:25 UTC QA Contact storage-qa-internal ashah
Anil Shah 2017-05-02 10:05:06 UTC Status ON_QA VERIFIED
Atin Mukherjee 2017-08-08 12:01:21 UTC Doc Text When a cloned volume is deleted, its brick paths (stored under /run/gluster/snaps) are not cleaned up correctly. This means that attempting to create a clone that has the same name as a previously cloned and deleted volume fails with a Commit failed message.

Workaround:
After deleting a cloned volume, ensure that brick entries in /run/gluster/snaps are unmounted and deleted, and that their logical volumes are removed.
Earlier when a cloned volume is deleted, its brick paths (stored under /run/gluster/snaps) are not cleaned up correctly. This means that attempting to create a clone that has the same name as a previously cloned and deleted volume fails with a Commit failed message. With this fix snapshot clone can be created with same names which were used earlier.
Doc Type Known Issue Bug Fix
Laura Bailey 2017-08-15 05:57:45 UTC Doc Text Earlier when a cloned volume is deleted, its brick paths (stored under /run/gluster/snaps) are not cleaned up correctly. This means that attempting to create a clone that has the same name as a previously cloned and deleted volume fails with a Commit failed message. With this fix snapshot clone can be created with same names which were used earlier. 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.
Flags needinfo?(asengupt)
Atin Mukherjee 2017-09-11 12:32:56 UTC Flags needinfo?(asengupt)
errata-xmlrpc 2017-09-21 00:53:11 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-09-21 04:25:52 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-07-14 05:21:51 UTC 2017-09-21 00:25:52 UTC

Back to bug 1309209