Bug 1260561 - transport and port should be optional arguments for glfs_set_volfile_server
Summary: transport and port should be optional arguments for glfs_set_volfile_server
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raghavendra Talur
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks: 1247933
TreeView+ depends on / blocked
 
Reported: 2015-09-07 09:18 UTC by Raghavendra Talur
Modified: 2016-06-16 13:35 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-16 13:35:09 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)
test to reproduce the issue (1.93 KB, text/x-csrc)
2015-09-07 09:22 UTC, Raghavendra Talur
no flags Details

Description Raghavendra Talur 2015-09-07 09:18:23 UTC
Description of problem:

Only server is the required argument for glfs_set_volfile_server
    and both transport and port are optional. When glfs_set_volfile_server
    is invocated multiple times, only on the first invocation we replace
    port 0 with 24007 and transport NULL with "localhost".
    
    Hence, replacing the parameters at the entry function is the right way.


How reproducible:
Always


Steps to Reproduce:
1. Download the attached program.
2. Find the readme within the file.
3. Follow the instructions.

Comment 1 Vijay Bellur 2015-09-07 09:19:53 UTC
REVIEW: http://review.gluster.org/12114 (gfapi: transport and port are optional for glfs_set_volfile_server) posted (#1) for review on master by Raghavendra Talur (rtalur@redhat.com)

Comment 2 Raghavendra Talur 2015-09-07 09:22:32 UTC
Created attachment 1070875 [details]
test to reproduce the issue

Comment 3 Vijay Bellur 2015-09-08 12:50:10 UTC
REVIEW: http://review.gluster.org/12114 (gfapi: transport and port are optional for glfs_set_volfile_server) posted (#2) for review on master by Raghavendra Talur (rtalur@redhat.com)

Comment 4 Niels de Vos 2016-06-16 13:35:09 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.