Bug 763563 (GLUSTER-1831)

Summary: "Failed to get transport public key" error on 20% of SP 3.1 additional server installations.
Product: [Retired] GlusterSP Reporter: Craig Carl <craig>
Component: coreAssignee: Timothy Asir <timothyasir>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: 3.1.0CC: platform, rahulcs, shireesh, timothyasir, vijay
Target Milestone: 3.1.2   
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: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screenshot of error on server being added.
none
Screenshot of error on existing node after error on new node. none

Description Craig Carl 2010-10-06 09:28:16 UTC
Created attachment 332

Comment 1 Craig Carl 2010-10-06 12:27:26 UTC
Screenshots attached. Same subnet, if I reboot the new node then restart the installation it usually works. The error appears to be random.

Comment 2 Craig Carl 2010-10-08 22:31:04 UTC
This bug will be resolved by eliminating the concept of storage pools.

Comment 3 Rahul C S 2010-12-07 04:37:25 UTC
Fixed in QA4. Please reopen if you find it again Craig.

Comment 4 Timothy Asir 2010-12-07 19:05:13 UTC
This bug is fixed.
Added functionalities to start rsync during restart fix this issue.