Bug 1696518

Summary:	builder203 does not have a valid hostname set
Product:	[Community] GlusterFS	Reporter:	Deepshikha khandelwal <dkhandel>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, mscherer
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-17 05:56:24 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 Deepshikha khandelwal 2019-04-05 04:51:44 UTC

Description of problem:


After reinstallation builder203 on AWS does not have a valid hostname set and hence it's network service might behave weird.

Comment 1 M. Scherer 2019-04-05 05:55:21 UTC

Can you be a bit more specific on:
- what network do behave weirdly ?

I also did set the hostname (using hostnamectl), so maybe this requires a reboot, and/or a different hostname.

Comment 2 M. Scherer 2019-04-05 07:02:14 UTC

So, answering to myself, rpc.statd didn't start after reboot, and the hostname was ip-172-31-38-158.us-east-2.compute.internal. After "hostnamectl set-hostname builder203.int.aws.gluster.org", that's better; Guess we need to automate that (as I used builder203.aws.gluster.org and this was wrong).

Comment 3 Deepshikha khandelwal 2019-04-17 05:56:24 UTC

Misc did set it up. Closing this one.