Bug 1265531 - Message ids in quota-messages.h should start from 120000 as opposed to 110000
Summary: Message ids in quota-messages.h should start from 120000 as opposed to 110000
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-23 07:33 UTC by Krutika Dhananjay
Modified: 2016-06-16 13:38 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of:
Environment:
Last Closed: 2016-06-16 13:38:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Krutika Dhananjay 2015-09-23 07:33:02 UTC
Description of problem:

While working on http://review.gluster.org/#/c/12217/, I figured that the message ids in the doxygen-friendly comments in quota-messages.h are supposed to start from 120000 whereas they seem to start from 110000.
This would cause these to conflict with the message ids for upcall xlator. What this means is that the extraction of messages using doxygen tool for the purpose of documentation could cause message-ids in the 110000+ series to have multiple diagnoses and recommended actions.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Manikandan 2015-10-19 06:53:21 UTC
Patch merged upstream : http://review.gluster.org/#/c/12218/

Comment 2 Niels de Vos 2016-06-16 13:38:14 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-3.8.0, please open a new bug report.

glusterfs-3.8.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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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