Bug 1665363 - Fix incorrect definition in index-mem-types.h
Summary: Fix incorrect definition in index-mem-types.h
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: index
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-11 07:04 UTC by Vijay Bellur
Modified: 2019-03-25 16:33 UTC (History)
1 user (show)

Fixed In Version: glusterfs-6.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-25 16:33:07 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 22011 0 None Merged features/index: Correct incorrect definition in header 2019-01-11 18:27:43 UTC

Description Vijay Bellur 2019-01-11 07:04:17 UTC 
Description of problem:

index-mem-types.h has the following definition:

#ifndef __QUIESCE_MEM_TYPES_H__
#define __QUIESCE_MEM_TYPES_H__

Clearly, a yank paste error that needs to be fixed.
Comment 1 Worker Ant 2019-01-11 07:09:07 UTC 
REVIEW: https://review.gluster.org/22011 (features/index: Correct incorrect definition in header) posted (#1) for review on master by Vijay Bellur
Comment 2 Worker Ant 2019-01-11 18:27:43 UTC 
REVIEW: https://review.gluster.org/22011 (features/index: Correct incorrect definition in header) posted (#2) for review on master by Amar Tumballi
Comment 3 Shyamsundar 2019-03-25 16:33:07 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-6.0, please open a new bug report.

glusterfs-6.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/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/
Note You need to log in before you can comment on or make changes to this bug.