Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1261742

Summary:	Tier: glusterd crash when trying to detach , when hot tier is having exactly one brick and cold tier is of replica type
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	tiering	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.7.5	CC:	bugs, nchilaka, vagarwal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1261741	Environment:
Last Closed:	2015-10-14 10:29:07 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:	1261741
Bug Blocks:	1260923

Description Mohammed Rafi KC 2015-09-10 06:04:39 UTC

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

Description of problem:
glusterd crash when trying to detach , when hot tier is having exactly one brick and cold tier with two bricks. This because of wrong calculation of subvols.


Version-Release number of selected component (if applicable):

mainline

How reproducible:

100%

Steps to Reproduce:
1.create a replica 2 volume with two bricks
2.attach a tier with one brick
3.detach the tier

Actual results:

crash

Expected results:

detach should success.

Additional info:

--- Additional comment from Vijay Bellur on 2015-09-10 02:04:29 EDT ---

REVIEW: http://review.gluster.org/12145 (tier/glusterd : Disable subvol match check during detach tier) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

Comment 1 Vijay Bellur 2015-09-14 14:03:05 UTC

REVIEW: http://review.gluster.org/12173 (tier/glusterd : Disable subvol match check during detach tier) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Pranith Kumar K 2015-10-14 10:29:07 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-glusterfs-3.7.5, please open a new bug report.

glusterfs-glusterfs-3.7.5 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://www.gluster.org/pipermail/gluster-users/2015-October/023968.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 3 Pranith Kumar K 2015-10-14 10:38:10 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.5, please open a new bug report.

glusterfs-3.7.5 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://www.gluster.org/pipermail/gluster-users/2015-October/023968.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user