[Bugs] [Bug 1739320] The result (hostname) of getnameinfo for all bricks (ipv6 addresses) are the same, while they are not.

bugzilla at redhat.com bugzilla at redhat.com
Sun Sep 1 05:49:40 UTC 2019


https://bugzilla.redhat.com/show_bug.cgi?id=1739320



--- Comment #21 from Mohit Agrawal <moagrawa at redhat.com> ---
Hi Amgad,

  Thanks for sharing the reply. I have checked the code. 
  We need to fix the issue to update transport-address family in case of client
process.

  For as of now I can provide a workaround to start shd with ipv6.
  You can copy the existing argument from the shd log file and add a string
--xlator-options 

  As per last shared logs last shd was spawned with below arguments

  /usr/sbin/glusterfs version 6.5 (args: /usr/sbin/glusterfs -s
2001:db8:1234::8 --volfile-id gluster/glustershd -p
/var/run/gluster/glustershd/glustershd.pid -l /var/log/glusterfs/glustershd.log
-S /var/run/gluster/3a1e3977fd7318f2.socket --xlator-option
*replicate*.node-uuid=8e2b40a7-098c-4f0a-b323-2e764bd315f3 --process-name
glustershd --client-pid=-6

  so start shd with enable ipv6 you can run like below after add
--xlator-option in command-line 
  arguments

  >>>>>>>>>>>>>>>

  /usr/sbin/glusterfs -s 2001:db8:1234::8 --volfile-id gluster/glustershd -p
/var/run/gluster/glustershd/glustershd.pid -l /var/log/glusterfs/glustershd.log
-S /var/run/gluster/3a1e3977fd7318f2.socket --xlator-option
*replicate*.node-uuid=8e2b40a7-098c-4f0a-b323-2e764bd315f3 --xlator-option
transport.address-family=inet6 --process-name glustershd --client-pid=-6 

  >>>>>>>>>>>>.

  I will upload a patch to resolve the same. 
  Let me know if you can test patch in your environment.

Thanks,
Mohit Agrawal

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Bugs mailing list