Bug 763670 (GLUSTER-1938)

Summary: Adding new storage node attached to wrong server
Product: [Retired] GlusterSP Reporter: Jacob Shucart <jacob>
Component: coreAssignee: Balamurugan Arumugam <bala>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: urgent    
Version: 3.1.0CC: platform
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Windows   
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:

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