Description of problem: When building a new volume on a brand new server I am unable to peer probe a 2nd node when creating a distributed volume. Version-Release number of selected component (if applicable): glusterfs-fuse-3.5.1-0.1.beta1.el6.x86_64 glusterfs-server-3.5.1-0.1.beta1.el6.x86_64 glusterfs-libs-3.5.1-0.1.beta1.el6.x86_64 glusterfs-api-3.5.1-0.1.beta1.el6.x86_64 glusterfs-cli-3.5.1-0.1.beta1.el6.x86_64 glusterfs-3.5.1-0.1.beta1.el6.x86_64 How reproducible: 1. Install the above packages from the Gluster Repo. 2. Create a new volume with 1 node. 3. try and peer probe the 2nd node. Actual results: Hostname: 172.16.242.241 Uuid: ad09b6f9-9e71-462b-bec0-bcdc93db221b State: Probe Sent to Peer (Connected) and on this node, gluster peer status times out with no output. Expected results: the 2nd node should join the pool Additional info: This makes GlusterFS UNUSABLE as a distributed filesystem!
Update: Still broken in 3.5.1-beta2.
You can close this bug, I've repreported it for the official 3.5.1 release: https://bugzilla.redhat.com/show_bug.cgi?id=1113460 *** This bug has been marked as a duplicate of bug 1113460 ***