Bug 1649843 (glusterfs-4.1.7)

Summary:	GlusterFS 4.1.7 tracker
Product:	[Community] GlusterFS	Reporter:	Shyamsundar <srangana>
Component:	core	Assignee:	Shyamsundar <srangana>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1	CC:	bugs, pasik
Target Milestone:	---	Keywords:	Tracking, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	glusterfs-4.1.6	Environment:
Last Closed:	2019-01-16 20:46:21 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:
Deadline:	2019-01-21

Description Shyamsundar 2018-11-14 15:55:57 UTC

Tracker bug for 4.1.7

Comment 1 Worker Ant 2019-01-16 20:23:46 UTC

REVIEW: https://review.gluster.org/22055 (doc: Release notes for 4.1.7) posted (#1) for review on release-4.1 by Shyamsundar Ranganathan

Comment 2 Worker Ant 2019-01-16 20:46:21 UTC

REVIEW: https://review.gluster.org/22055 (doc: Release notes for 4.1.7) merged (#1) on release-4.1 by Shyamsundar Ranganathan

Comment 3 Shyamsundar 2019-01-22 14:09:20 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-4.1.7, please open a new bug report.

glusterfs-4.1.7 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] https://lists.gluster.org/pipermail/announce/2019-January/000118.html
[2] https://www.gluster.org/pipermail/gluster-users/