Bug 1594908 (glusterfs-4.1.2)

Summary:	GlusterFS 4.1.2 tracker
Product:	[Community] GlusterFS	Reporter:	Shyamsundar <srangana>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1	CC:	bugs, kkeithle, redhat
Target Milestone:	---	Keywords:	Tracking, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-30 18:57: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:

Description Shyamsundar 2018-06-25 16:42:37 UTC

Tracker for the release 4.1.2

Comment 1 Worker Ant 2018-07-23 23:40:30 UTC

REVIEW: https://review.gluster.org/20552 (doc: Correct release notes to remove py3 support) posted (#1) for review on release-4.1 by Shyamsundar Ranganathan

Comment 2 Worker Ant 2018-07-24 10:29:15 UTC

COMMIT: https://review.gluster.org/20552 committed in release-4.1 by "Shyamsundar Ranganathan" <srangana> with a commit message- doc: Correct release notes to remove py3 support

Updates: bz#1594908

Change-Id: I6cefb3b6abc1b38981da4959f1be24814be6888c
Signed-off-by: ShyamsundarR <srangana>

Comment 3 Worker Ant 2018-07-24 12:40:10 UTC

REVIEW: https://review.gluster.org/20560 (doc: Added release notes for 4.1.2) posted (#1) for review on release-4.1 by Shyamsundar Ranganathan

Comment 4 Worker Ant 2018-07-24 13:00:37 UTC

COMMIT: https://review.gluster.org/20560 committed in release-4.1 by "Shyamsundar Ranganathan" <srangana> with a commit message- doc: Added release notes for 4.1.2

Fixes: bz#1594908
Change-Id: I93db801c1292b8f57e35157ce2b503fefa6cb2f2
Signed-off-by: ShyamsundarR <srangana>

Comment 5 Shyamsundar 2018-07-30 18:57:21 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.2, please open a new bug report.

glusterfs-4.1.2 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/2018-July/000106.html
[2] https://www.gluster.org/pipermail/gluster-users/