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

Bug 1960691

Summary: hostname set to localhost
Product: OpenShift Container Platform Reporter: Sonigra Saurab <ssonigra>
Component: RHCOSAssignee: RHCOS Bug Triage <rhcos-triage>
Status: CLOSED DUPLICATE QA Contact: Michael Nguyen <mnguyen>
Severity: high Docs Contact:
Priority: low    
Version: 4.6CC: aos-bugs, dornelas, harpatil, jligon, miabbott, mrussell, nstielau, smilner, travier, walters
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-17 16:42:07 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 Sonigra Saurab 2021-05-14 15:25:41 UTC
Description of problem:

Hostname of the node set to localhost on AWS cluster.


Actual results:

hostname of the node changes to localhost

Expected results:

hostname should remain intact


Additional info:


The issue is similar to bug https://bugzilla.redhat.com/show_bug.cgi?id=1501193 but the bug is for RHEL 7 and the issue is also faced in RHCOS

Comment 2 Timothée Ravier 2021-05-17 08:07:41 UTC
Could you provide at least the following:

OCP Version at Install Time:
RHCOS Version at Install Time:
OCP Version after Upgrade (if applicable):
RHCOS Version after Upgrade (if applicable):

Platform: AWS
Architecture: x86_64

What are the steps to reproduce your issue? Is this a new installation or an update?

Comment 3 Micah Abbott 2021-05-17 13:44:35 UTC
I'm sorry, but this is a poor quality BZ that has almost no useful information for engineering to work with.

> The issue is similar to bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1501193 but the bug is for RHEL
> 7 and the issue is also faced in RHCOS

RHCOS is based on RHEL 8 and it seems unlikely they are the same issue.


We have a template in place for new BZs against the RHCOS component that seems to have been completely ignored.

Before we can take any action on this BZ, please provide the following information.


OCP Version at Install Time:
RHCOS Version at Install Time:
OCP Version after Upgrade (if applicable):
RHCOS Version after Upgrade (if applicable):
Platform: AWS, Azure, bare metal, GCP, vSphere, etc
Architecture: x86_64/ppc64le/s390x

What are you trying to do? What is your use case?


What happened? What went wrong or what did you expect?


What are the steps to reproduce your issue? Please try to reduce these steps to something that can be reproduced with a single RHCOS node.


If you're having problems booting/installing RHCOS, please provide:
- the full contents of the serial console showing disk initialization, network configuration, and Ignition stage (see https://access.redhat.com/articles/7212 for information about configuring your serial console)
- Ignition JSON
- output of `journalctl -b`


If you're having problems post-upgrade, please provide:
- A complete must-gather (`oc adm must-gather`)


If you're having SELinux related issues, please provide:
- The full `/var/log/audit/audit.log` file
- Were any SELinux modules or booleans changed from the default configuration?
- The output of `ostree admin config-diff | grep selinux/targeted` on impacted nodes


Please add anything else that might be useful, for example:
- kernel command line (`cat /proc/cmdline`)
- contents of `/etc/NetworkManager/system-connections/`
- contents of `/etc/sysconfig/network-scripts/`

Comment 4 Colin Walters 2021-05-17 13:58:37 UTC
Based on:

 May 13 12:22:38 localhost systemd-hostnamed[3338724]: Failed to read hostname and machine information: Is a directory

This is ikely a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1921937

*** This bug has been marked as a duplicate of bug 1921937 ***

Comment 6 Colin Walters 2021-05-17 16:42:07 UTC

*** This bug has been marked as a duplicate of bug 1921937 ***