[Bugs] [Bug 1374584] New: Detach tier commit is allowed when detach tier start goes into failed state

bugzilla at redhat.com bugzilla at redhat.com
Fri Sep 9 07:01:41 UTC 2016


            Bug ID: 1374584
           Summary: Detach tier commit is allowed when detach tier start
                    goes into failed state
           Product: GlusterFS
           Version: mainline
         Component: tiering
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: hgowtham at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org, hgowtham at redhat.com,
                    kramdoss at redhat.com
        Depends On: 1374412

+++ This bug was initially created as a clone of Bug #1374412 +++

Description of problem:
Detach tier commit operation should not be allowed when detach tier start
operation has gone into failed state. There might be files which are not moved
from hot to cold tier when a detach tier operation fails. Allowing to commit
the operation removes off the hot tier bricks, thereby making those data in hot
tier inaccessible.

Version-Release number of selected component (if applicable):
rpm -qa | grep 'gluster'

How reproducible:

Steps to Reproduce:
1. create a tier vol and start detach tier operation
2. kill a brick on hot tier and restore it after a while to fail the detach
tier operation
3. Try detach tier commit

Actual results:
detach tier commit is allowed

Expected results:
detach tier commit should not be allowed

Additional info:

Referenced Bugs:

[Bug 1374412] Detach tier commit is allowed when detach tier start goes
into failed state
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list