Bug 1157334

Summary:	[SNAPSHOT]: snapshot should be deactivated by default when created
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	snapshot	Assignee:	Vijaikumar Mallikarjuna <vmallika>
Status:	CLOSED ERRATA	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	divya, rhinduja, rhs-bugs, rjoseph, smohan, storage-qa-internal, surs
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.0.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	SNAPSHOT
Fixed In Version:	glusterfs-3.6.0.33-1	Doc Type:	Enhancement
Doc Text:	Active snapshots consume similar resources as a regular volume. Therefore, to reduce the resource consumption, newly created snapshots will be in deactivated state, by default. New snapshot configuration option "activate-on-create" has been added to configure the default option. You must explicitly activate new snapshots manually for accessing that snapshot.	Story Points:	---
Clone Of:
Clones:	1157991 (view as bug list)		Environment:
Last Closed:	2015-01-15 13:41:06 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:	1157991, 1162694, 1170921

Description Vijaikumar Mallikarjuna 2014-10-27 03:59:04 UTC

Description of problem:

Currently snapshot is activated when it is created.
By default snapshot should be de-activated when it is created and this behavior should be configurable.

Comment 2 Vijaikumar Mallikarjuna 2014-11-12 11:30:22 UTC

Patch submitted: https://code.engineering.redhat.com/gerrit/#/c/36484/

Comment 4 Divya 2015-01-08 07:40:24 UTC

Rajesh,

Please review the edited doc text and sign-off.

Comment 7 errata-xmlrpc 2015-01-15 13:41:06 UTC

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://rhn.redhat.com/errata/RHBA-2015-0038.html