Red Hat Bugzilla – Full Text Bug Listing
|Summary:||3.3beta2 Glusterd Connectivity Issue right after installation|
|Product:||[Community] GlusterFS||Reporter:||Veda Shankar <vshankar>|
|Component:||glusterd||Assignee:||Amar Tumballi <amarts>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:|
|Version:||3.3-beta||CC:||gluster-bugs, vijay, vraman|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Veda Shankar 2011-10-07 12:15:18 EDT
Created attachment 699
Comment 1 Veda Shankar 2011-10-07 15:14:04 EDT
I wanted to test the 3.3beta2 installation. I started a Centos 5.6 64 bit AMI (not Gluster, vanilla Centos) and successfully built GlusterFS from the source in glusterfs-3.3beta2.tar.gz. I followed our documentation (Gluster_Unified_File_and_Object_Storage.pdf) and installed the object-storage tarball and executed centos_install.sh without any issues. But when I execute gluster volume create auth ip-10-245-194-250:/export/auth/ I get: Connection failed. Please check if gluster daemon is operational. glusterd is running and gluster –V reports 3.3beta2. I am attaching the .log from that system, I suspect it is the transport-type in the .vol file. I am also including the access for that system and the PEM key so that you can log into the system. I did a similar exercise yesterday with the S appliance and ran into the same problem. Install VSA, repo switch to 3.2.3 Gluster volume info command worked Repo switch to 3.3beta2 Gluster volume info command failed. The error condition is the same as the test with source code.
Comment 2 Veda Shankar 2011-10-07 16:50:53 EDT
I did the following steps to fix the issue: insmod /lib/modules/18.104.22.168-2.fc8xen/kernel/net/ipv6/ipv6.ko modprobe ipv6 service glusterd restart I will leave the bug open for another day in case we want to add any more comments.