Bug 762261 (GLUSTER-529)

Summary:	wrong hostname incrementation upon subsequent server installation
Product:	[Retired] GlusterSP	Reporter:	Harshavardhana <fharshav>
Component:	core	Assignee:	Balamurugan Arumugam <bala>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	cww, pavan, platform, webteam
Target Milestone:	3.0.3
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:

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.