Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1038866

Summary:	[FEAT] command to rename peer hostname
Product:	[Community] GlusterFS	Reporter:	DS <redhat+bugzilla>
Component:	cli	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, charlesalva, joe, kwade, nicolas, okane, sam.wouters
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-20 09:08:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description DS 2013-12-06 01:09:26 UTC

Renaming a peers hostname seems to require manually rewriting (automatically generated) configuration files. The "peer probe" command only allows limited renaming during initialization.

There should be a new command (or maybe an extended "peer probe") that allows changing the hostname of a peer including all the bricks. (Changes regarding bricks are currently required, but shouldn't be, as described in Bug 765437.)

Comment 1 Niels de Vos 2014-09-18 05:53:20 UTC

*** Bug 1049470 has been marked as a duplicate of this bug. ***

Comment 2 Joe Julian 2017-01-10 22:39:26 UTC

This comes up frequently on IRC. Could we bump the severity?

Comment 4 okane 2018-09-12 14:11:42 UTC

+10 vote for a utility to manage the "known peer" connection information.
I have added a new storage network  to my ovirt/gluster system but I can not remove the "VM data" network from the servers.

Comment 5 Vijay Bellur 2018-11-20 09:36:18 UTC

Migrated to github:

https://github.com/gluster/glusterfs/issues/587

Please follow the github issue for further updates on this bug.