Bug 1696518 - builder203 does not have a valid hostname set
Summary: builder203 does not have a valid hostname set
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-05 04:51 UTC by Deepshikha khandelwal
Modified: 2019-04-17 05:56 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-04-17 05:56:24 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.