Bug 1629877 - GlusterFS can be improved (clone for Gluster-5)
Summary: GlusterFS can be improved (clone for Gluster-5)
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: unclassified
Version: 5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-17 14:39 UTC by Shyamsundar
Modified: 2020-03-12 13:22 UTC (History)
1 user (show)

Fixed In Version: glusterfs-5.0
Doc Type: Enhancement
Doc Text:
Clone Of: 1193929
Environment:
Last Closed: 2020-03-12 13:22:09 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22855 0 None Open tests/utils: Fix py2/py3 util python scripts 2019-07-01 07:02:23 UTC

Description Shyamsundar 2018-09-17 14:39:57 UTC
+++ This bug was initially created as a clone of Bug #1193929 +++

I hope this bug is never fixed.

The upstream patch process requires that each patch have an associated bug ID before it can be merged.  However, there is no requirement that the bug contain any information or receive any kind of signoff before the patch can proceed.  As a result, many of our developers have the habit of creating such "placeholder" bugs every time they want to make a change, even if it's just a random cleanup/idea and not an actual bug fix or requested/tracked feature request.  Also, any patch with the dreaded "rfc" bug ID (which would be appropriate for such changes) is unlikely to be reviewed.

This bug exists to satisfy our process requirement, without the additional negatives of clogging up our triage/tracking processes and making it appear that the code has more bugs (which would be bad) when in fact a developer had more ideas (which is generally good).

Comment 1 Worker Ant 2018-09-17 14:44:10 UTC
REVIEW: https://review.gluster.org/21195 (gfapi: Cleanup alias file) posted (#1) for review on release-5 by Shyamsundar Ranganathan

Comment 2 Worker Ant 2018-09-17 19:30:20 UTC
COMMIT: https://review.gluster.org/21195 committed in release-5 by "Shyamsundar Ranganathan" <srangana> with a commit message- gfapi: Cleanup alias file

2 extra symbols were in the alias file, that are not exported
this is cleaned up with this patch.

Change-Id: I1ab54b9fb6b0d455884fbbfd89820c60bb861e6f
Updates: bz#1629877
Signed-off-by: ShyamsundarR <srangana>

Comment 3 Shyamsundar 2018-10-23 15:19:00 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.0, please open a new bug report.

glusterfs-5.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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/

Comment 4 Worker Ant 2019-06-12 06:33:48 UTC
REVIEW: https://review.gluster.org/22855 (tests/utils: Fix py2/py3 util python scripts) posted (#1) for review on release-5 by hari gowtham

Comment 5 Worker Ant 2019-07-01 07:02:25 UTC
REVIEW: https://review.gluster.org/22855 (tests/utils: Fix py2/py3 util python scripts) merged (#3) on release-5 by hari gowtham

Comment 6 Worker Ant 2020-03-12 13:22:09 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/1001, and will be tracked there from now on. Visit GitHub issues URL for further details


Note You need to log in before you can comment on or make changes to this bug.