Bug 1276617

Summary: CTR should be enabled on attach tier, disabled otherwise.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nag Pavan Chilakam <nchilaka>
Component: tierAssignee: Bug Updates Notification Mailing List <rhs-bugs>
Status: CLOSED DUPLICATE QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: urgent Docs Contact:
Priority: urgent    
Version: rhgs-3.1CC: bugs, dlambrig, rhs-bugs, storage-qa-internal
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1274847 Environment:
Last Closed: 2015-11-01 16:49:12 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: 1274847, 1276671, 1276678    
Bug Blocks: 1260923    

Description Nag Pavan Chilakam 2015-10-30 10:12:02 UTC
We need this at highest priority
+++ This bug was initially created as a clone of Bug #1274847 +++

CTR is currently disabled by default, and must be manually enabled for tiering to start. This is an overhead on the administrator and easy to overlook. Enable it automatically when a tier is attached.

--- Additional comment from Vijay Bellur on 2015-10-23 12:12:36 EDT ---

REVIEW: http://review.gluster.org/12420 (cluster/tier enable CTR on attach tier) posted (#1) for review on master by Dan Lambright (dlambrig)

--- Additional comment from Vijay Bellur on 2015-10-28 10:45:41 EDT ---

REVIEW: http://review.gluster.org/12420 (cluster/tier enable CTR on attach tier) posted (#2) for review on master by Dan Lambright (dlambrig)

--- Additional comment from Vijay Bellur on 2015-10-29 15:42:23 EDT ---

REVIEW: http://review.gluster.org/12420 (cluster/tier enable CTR on attach tier) posted (#3) for review on master by Dan Lambright (dlambrig)

Comment 2 Dan Lambright 2015-11-01 16:49:12 UTC

*** This bug has been marked as a duplicate of bug 1276678 ***