Bug 763563 (GLUSTER-1831) - "Failed to get transport public key" error on 20% of SP 3.1 additional server installations.
Summary: "Failed to get transport public key" error on 20% of SP 3.1 additional server...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1831
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.1.0
Hardware: All
OS: Linux
low
high
Target Milestone: 3.1.2
Assignee: Timothy Asir
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-06 12:27 UTC by Craig Carl
Modified: 2010-12-07 22:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)
screenshot of error on server being added. (16.47 KB, image/png)
2010-10-06 09:27 UTC, Craig Carl
no flags Details
Screenshot of error on existing node after error on new node. (46.46 KB, image/png)
2010-10-06 09:28 UTC, Craig Carl
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.