Bug 762293 (GLUSTER-561)

Summary: with address family set to 'inet-sdp', transport/socket doesn't work correctly
Product: [Community] GlusterFS Reporter: Raghavendra G <raghavendra>
Component: transportAssignee: Raghavendra G <raghavendra>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 2.0.9CC: aavati, gluster-bugs, lakshmipathi, rabhat
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Raghavendra G 2010-01-22 05:13:35 UTC 
*** Bug 515 has been marked as a duplicate of this bug. ***
Comment 1 Raghavendra G 2010-01-22 08:12:54 UTC 
The sa_family member of sockaddr struct passed to calls connect, bind etc is set to AF_INET_SDP. The correct way is to use address family AF_INET_SDP only during call to socket system call and for all other calls, address family should be specified as AF_INET.
Comment 2 Anand Avati 2010-01-22 10:21:47 UTC 
PATCH: http://patches.gluster.com/patch/2671 in release-2.0 (transport/socket: use appropriate address family macro when address family is inet-sdp.)
Comment 3 Anand Avati 2010-01-22 10:34:38 UTC 
PATCH: http://patches.gluster.com/patch/2672 in master (transport/socket: use appropriate address family macro when address family is inet-sdp.)
Comment 4 Anand Avati 2010-01-28 11:11:36 UTC 
PATCH: http://patches.gluster.com/patch/2714 in master (transport/socket: guess an appropriate address family when it is not specified in configuration.)
Comment 5 Anand Avati 2010-01-28 11:11:44 UTC 
PATCH: http://patches.gluster.com/patch/2713 in release-2.0 (transport/socket: guess an appropriate address family when it is not specified in configuration.)
Comment 6 Raghavendra Bhat 2010-02-10 07:59:15 UTC 
It seems to be a problem specific to some hardware. Could not reproduce it locally. Hence not moving it to the verified state.
Comment 7 Anand Avati 2010-03-31 05:41:04 UTC 
PATCH: http://patches.gluster.com/patch/3043 in release-3.0 (transport/socket: guess an appropriate address family when it is not specified in configuration.)