Bug 763670 (GLUSTER-1938) - Adding new storage node attached to wrong server
Summary: Adding new storage node attached to wrong server
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-1938
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.1.0
Hardware: All
OS: Windows
urgent
high
Target Milestone: ---
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-12 21:08 UTC by Jacob Shucart
Modified: 2010-11-02 04:32 UTC (History)
1 user (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)
Add an attachment (proposed patch, testcase, etc.)

Description Jacob Shucart 2010-10-12 21:08:19 UTC 
I installed a new Platform 3.1.0 server.  I then created a new VM and was going to add it as a server to the console I had just started.  I initiated the add process in the server and then booted the new VM only to have it start talking to a different Platform server than the one I was trying to add it to...
Comment 1 Balamurugan Arumugam 2010-10-13 06:36:55 UTC 
This can be done by passing dhcp=PORTNUMBER kernel boot parameter on management console server and new server boot time.  By default, port number 68 is used in management console and new server.
Comment 2 Balamurugan Arumugam 2010-10-29 04:01:22 UTC 
Does this option work to fix this issue?
Comment 3 Balamurugan Arumugam 2010-11-02 01:32:14 UTC 
Closing the bug
Note You need to log in before you can comment on or make changes to this bug.