Bug 762261 (GLUSTER-529) - wrong hostname incrementation upon subsequent server installation
Summary: wrong hostname incrementation upon subsequent server installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-529
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: 3.0.3
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-09 05:47 UTC by Harshavardhana
Modified: 2015-03-23 01:03 UTC (History)
4 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)
Add an attachment (proposed patch, testcase, etc.)

Description Harshavardhana 2010-01-09 05:47:05 UTC 
If we provide a hostname for example "gluster001" for a master node then subsequent slave nodes should get host name in pattern of "gluster002, gluster003, ....gluster00N" . But in Storage Platform we observed the trailing zeroes were removed when the "installer-info" returns back with WebUI window prefilled with hostnames of pattern "gluster1 gluster2 glusterN". Now this seems wrong in accordance with the master node hostname. We did eventual installation by changing the hostname at "Add Server" window.
Comment 1 Harshavardhana 2010-01-28 04:55:35 UTC 
There is work around for this bug as we provided to edit the hostname during installation resulting in user to make choices of hostnames he wanted to provide for each machines.
Comment 2 Harshavardhana 2010-10-15 22:35:19 UTC 
This functionality has been revamped in 3.1 closing as resolved.
Note You need to log in before you can comment on or make changes to this bug.