Bug 1510324 - Master branch is broken because of the conflicts
Summary: Master branch is broken because of the conflicts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohammed Rafi KC
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-07 08:35 UTC by Mohammed Rafi KC
Modified: 2018-03-15 11:20 UTC (History)
1 user (show)

Fixed In Version: glusterfs-4.0.0
Clone Of:
Environment:
Last Closed: 2018-03-15 11:20:03 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Mohammed Rafi KC 2017-11-07 08:35:29 UTC
Description of problem:

An argument from the caller of rpcsvc_program_register was missed because of the conflicts between I45c3dcdbf39ec90ba39d914432d13a2ace00a5ee and Id0a2da3632516dc1a5560dde2b151b2e5f0be8e5

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-11-07 08:36:51 UTC
REVIEW: https://review.gluster.org/18680 (protocol/server: Add an argument to rpcsvc_program_register) posted (#1) for review on master by mohammed rafi  kc

Comment 2 Worker Ant 2017-11-07 12:02:07 UTC
COMMIT: https://review.gluster.org/18680 committed in master by  

------------- protocol/server: Add an argument to rpcsvc_program_register

Because of the conflicts between changes [1] and [2], a new argument
was missed from the caller of rpcsvc_program_register.

[1] : Id0a2da3632516dc1a5560dde2b151b2e5f0be8e5
[2] : I45c3dcdbf39ec90ba39d914432d13a2ace00a5ee

Change-Id: If53f755727f1bb23e0b9fb45ebf25fbc80d770a2
BUG: 1510324
Signed-off-by: Mohammed Rafi KC <rkavunga>

Comment 3 Mohammed Rafi KC 2017-11-07 13:51:00 UTC
https://review.gluster.org/#/c/18680

Comment 4 Shyamsundar 2018-03-15 11:20:03 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.0.0, please open a new bug report.

glusterfs-4.0.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://lists.gluster.org/pipermail/announce/2018-March/000092.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.