Bug 1956360 - Node coming up from a reboot with 'localhost' hostname in a baremetal IPI cluster.
Summary: Node coming up from a reboot with 'localhost' hostname in a baremetal IPI clu...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.0
Assignee: Tomas Sedovic
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-03 14:24 UTC by Sabina Aledort
Modified: 2024-12-20 19:59 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-18 09:13:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sabina Aledort 2021-05-03 14:24:09 UTC
Version: 4.8.0-0.nightly-2021-04-30-201824

$ openshift-install version
4.8.0-0.nightly-2021-04-30-201824

Platform:
baremetal

Please specify:
IPI

What happened?

Node coming up from a reboot with 'localhost' hostname in a baremetal IPI cluster.

[root@cnfdd5-installer ~]# oc get node
NAME                                             STATUS                        ROLES                     AGE     VERSION
cnfdd5.clus2.t5g.lab.eng.bos.redhat.com          Ready                         worker,worker-cnf         5h31m   v1.21.0-rc.0+aa1dc1f
cnfdd7.clus2.t5g.lab.eng.bos.redhat.com          Ready                         worker,worker-cnf         5h34m   v1.21.0-rc.0+aa1dc1f
cnfdd8.clus2.t5g.lab.eng.bos.redhat.com          Ready                         worker,worker-duprofile   5h38m   v1.21.0-rc.0+aa1dc1f
dhcp19-17-115.clus2.t5g.lab.eng.bos.redhat.com   Ready                         master,virtual            6h19m   v1.21.0-rc.0+aa1dc1f
dhcp19-17-116.clus2.t5g.lab.eng.bos.redhat.com   Ready                         master,virtual            6h20m   v1.21.0-rc.0+aa1dc1f
dhcp19-17-117.clus2.t5g.lab.eng.bos.redhat.com   Ready                         master,virtual            6h20m   v1.21.0-rc.0+aa1dc1f

After reboot:

[root@cnfdd5-installer cnf-internal-deploy]# ssh core.t5g.lab.eng.bos.redhat.com
Red Hat Enterprise Linux CoreOS 48.84.202104301525-0
  Part of OpenShift 4.8, RHCOS is a Kubernetes native operating system
  managed by the Machine Config Operator (`clusteroperator/machine-config`).

WARNING: Direct SSH access to machines is not recommended; instead,
make configuration changes via `machineconfig` objects:
  https://docs.openshift.com/container-platform/4.8/architecture/architecture-rhcos.html

---
Last login: Mon May  3 07:38:08 2021 from 10.19.17.175
[systemd]
Failed Units: 2
  NetworkManager-wait-online.service
  node-valid-hostname.service
[core@localhost ~]$ hostname
localhost

After another reboot:

[root@cnfdd5-installer cnf-internal-deploy]# ssh core.t5g.lab.eng.bos.redhat.com
Red Hat Enterprise Linux CoreOS 48.84.202104301525-0
  Part of OpenShift 4.8, RHCOS is a Kubernetes native operating system
  managed by the Machine Config Operator (`clusteroperator/machine-config`).

WARNING: Direct SSH access to machines is not recommended; instead,
make configuration changes via `machineconfig` objects:
  https://docs.openshift.com/container-platform/4.8/architecture/architecture-rhcos.html

---
Last login: Mon May  3 10:15:59 2021 from 10.19.17.175
[systemd]
Failed Units: 2
  NetworkManager-wait-online.service
  stalld.service
[core@cnfdd5 ~]$ hostname
cnfdd5.clus2.t5g.lab.eng.bos.redhat.com


What did you expect to happen?
The node should appear with its proper fqdn after a reboot.

Anything else we need to know?
Might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1929160

Comment 9 Red Hat Bugzilla 2023-09-15 01:33:50 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days


Note You need to log in before you can comment on or make changes to this bug.