Bug 1238593

Summary: tiering/snapshot: Tier daemon failed to start during volume start after restoring into a tiered volume from a non-tiered volume.
Product: [Community] GlusterFS Reporter: Mohammed Rafi KC <rkavunga>
Component: tieringAssignee: Mohammed Rafi KC <rkavunga>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: bugs, dlambrig
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1254442 (view as bug list) Environment:
Last Closed: 2016-06-16 13:18:34 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: 1254442, 1260923    

Description Mohammed Rafi KC 2015-07-02 08:48:39 UTC
Description of problem:

 Tier daemon failed to start during volume start after restoring into a tiered volume from a non-tiered volume.

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


How reproducible:

100%.

Steps to Reproduce:
1.create a tiered volume
2.take snapshot of the tiered volume
3.detach-tier
4.stop the volume
5.restore the snapshot
6.start the volume
7.chek #gluster v rebalance volname tier status

Actual results:

tier daemon is not running

Expected results:

tier daemon should along with volume start

Additional info:

Comment 1 Anand Avati 2015-07-03 12:01:57 UTC
REVIEW: http://review.gluster.org/11525 (tiering/glusterd: start tier daemon during volume start) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

Comment 2 Anand Avati 2015-07-06 07:03:07 UTC
REVIEW: http://review.gluster.org/11525 (tiering/glusterd: start tier daemon during volume start) posted (#2) for review on master by mohammed rafi  kc (rkavunga)

Comment 3 Anand Avati 2015-07-07 07:06:44 UTC
REVIEW: http://review.gluster.org/11525 (tiering/glusterd: start tier daemon during volume start) posted (#3) for review on master by mohammed rafi  kc (rkavunga)

Comment 4 Anand Avati 2015-07-20 16:27:35 UTC
REVIEW: http://review.gluster.org/11525 (tiering/glusterd: start tier daemon during volume start) posted (#4) for review on master by Dan Lambright (dlambrig)

Comment 5 Anand Avati 2015-08-04 14:47:22 UTC
REVIEW: http://review.gluster.org/11525 (tiering/glusterd: start tier daemon during volume start) posted (#5) for review on master by mohammed rafi  kc (rkavunga)

Comment 6 Anand Avati 2015-08-06 06:39:54 UTC
REVIEW: http://review.gluster.org/11525 (tiering/glusterd: start tier daemon during volume start) posted (#6) for review on master by mohammed rafi  kc (rkavunga)

Comment 7 Anand Avati 2015-08-06 21:38:15 UTC
REVIEW: http://review.gluster.org/11525 (tiering/glusterd: start tier daemon during volume start) posted (#7) for review on master by Dan Lambright (dlambrig)

Comment 8 Nagaprasad Sathyanarayana 2015-10-25 15:09:46 UTC
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 9 Niels de Vos 2016-06-16 13:18:34 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.8.0, please open a new bug report.

glusterfs-3.8.0 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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user