Description of problem: ======================= After volume restart the tier detach stop failing with error message "volume detach-tier stop: failed: Detach-tiernot started" and detach-tier commit is removing the tier. Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.7.5-5 How reproducible: ================= 100% Steps to Reproduce: =================== 1.Have a two node cluster 2.Create a replica (1*2) volume using two nodes and start it. 3.Attach tier of type Distributes (1*1) 4.Restart the volume // gluster volume <vol_name> start force 5.Stop the detach tier // it will fail 6.Do detach tier commit // it will pass Actual results: =============== After volume restart, unable to stop the started detach tier Expected results: ================ Should be able to stop the detach tier even after volume restart. Additional info:
Small correction in reproducing steps: ====================================== 1.Have a two node cluster 2.Create a replica (1*2) volume using two nodes and start it. 3.Attach tier of type Distributes (1*1) 4.Start the detach tier ****missed this step previously***** 5.Restart the volume // gluster volume <vol_name> start force 6.Stop the detach tier // it will fail 7.Do detach tier commit // it will pass
I will try to reproduce it. and update the bug before 20th jan evening
It works on the upstream, master.
The patch set to the upstream master to fix this is: http://review.gluster.org/#/c/12833/ the patch for 3.7.6 is: http://review.gluster.org/#/c/12921/
The downstream patch is: https://code.engineering.redhat.com/gerrit/#/c/63464/
From the mail, the conversion: The bug 1279314 was marked as known issue. When we were trying to document that, we learned it was fixed and then removed from the tracker. The RCA for both the bugs turned out to be same and hence fixed with 1284387. Please note the patch in 2 was merged with 1284387, which is fully acked. Regards, Vivek
Marking this as verified.
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-2016-0193.html