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

Bug 1097725

Summary:	[SNAPSHOT]: missed snaps list doesn not capture missed snap creates/deletes/restores
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	glusterd	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	pre-release	CC:	bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1097734 1098070 (view as bug list)		Environment:
Last Closed:	2014-11-11 08:32:32 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:	1097734, 1098070

Description Avra Sengupta 2014-05-14 12:13:44 UTC

Description of problem:
When one brick is down and snap force option is used, snap creation is successful but missed_snap_list does not display the missed snaps


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2014-05-14 12:52:25 UTC

REVIEW: http://review.gluster.org/7764 (glusterd/snapshot: Putting back the missed_snaps_list code) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Anand Avati 2014-05-15 07:40:34 UTC

COMMIT: http://review.gluster.org/7764 committed in master by Kaushal M (kaushal) 
------
commit 745347c8a2374442b8be69c7245d585289541e1b
Author: Avra Sengupta <asengupt>
Date:   Wed May 14 05:17:13 2014 +0000

    glusterd/snapshot: Putting back the missed_snaps_list code
    
    Setting of missed_snap_count was removed as part of an
    earlier patch. Putting back the code.
    Signed-off-by: Avra Sengupta <asengupt>
    
    Change-Id: Ib6412d6100145e94d10f6f4a8a1fe4e645c1a69e
    BUG: 1097725
    Reviewed-on: http://review.gluster.org/7764
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Kaushal M <kaushal>

Comment 3 Niels de Vos 2014-09-22 12:40:24 UTC

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:32:32 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users