Bug 1659085 (glusterfs-5.3)

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

Description Shyamsundar 2018-12-13 14:30:31 UTC

Tracker for the release 5.3

Comment 1 Worker Ant 2019-01-16 20:28:52 UTC

REVIEW: https://review.gluster.org/22056 (doc: Release notes for 5.3) posted (#1) for review on release-5 by Shyamsundar Ranganathan

Comment 2 Worker Ant 2019-01-16 20:42:57 UTC

REVIEW: https://review.gluster.org/22056 (doc: Release notes for 5.3) merged (#1) on release-5 by Shyamsundar Ranganathan

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

glusterfs-5.3 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/