Bug 1950763 - Node registered as localhost.localdomain in a baremetal IPI cluster
Summary: Node registered as localhost.localdomain in a baremetal IPI cluster
Keywords:
Status: CLOSED DUPLICATE of bug 1929160
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Beth White
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-18 13:07 UTC by Sabina Aledort
Modified: 2021-04-20 16:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-20 16:18:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
journalctl.log (4.16 MB, text/plain)
2021-04-18 13:20 UTC, Sabina Aledort
no flags Details
must-gather (1.07 MB, application/gzip)
2021-04-18 13:22 UTC, Sabina Aledort
no flags Details

Description Sabina Aledort 2021-04-18 13:07:34 UTC
Version: 4.8.0-0.nightly-2021-04-18-073623

$ openshift-install version
4.8.0-0.nightly-2021-04-18-073623

Platform:
baremetal

Please specify: IPI

What happened?

When installing a new baremetal IPI cluster, one of the masters came up as localhost.localdomain.

[root@cnfdc2-installer ~]# oc get node
NAME                                             STATUS     ROLES    AGE   VERSION
dhcp19-17-121.clus2.t5g.lab.eng.bos.redhat.com   NotReady   master   26m   v1.21.0-rc.0+2993be8
dhcp19-17-122.clus2.t5g.lab.eng.bos.redhat.com   NotReady   master   26m   v1.21.0-rc.0+2993be8
localhost                                        NotReady   master   20m   v1.21.0-rc.0+2993be8

What did you expect to happen?

All 3 masters should appear with their proper fqdn.

We had a similar bug in 4.7 that was fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1929160

Adding cluster must-gather and journalctl log from the 'localhost' node.

Comment 1 Sabina Aledort 2021-04-18 13:20:57 UTC
Created attachment 1773036 [details]
journalctl.log

Comment 2 Sabina Aledort 2021-04-18 13:22:03 UTC
Created attachment 1773037 [details]
must-gather

Comment 3 Sabina Aledort 2021-04-18 15:48:01 UTC
It is happening in other clusters as well.

[root@cnfdc2-installer ~]# oc get node
NAME                                             STATUS   ROLES    AGE   VERSION
dhcp19-17-122.clus2.t5g.lab.eng.bos.redhat.com   Ready    master   66m   v1.21.0-rc.0+2993be8
localhost                                        Ready    master   62m   v1.21.0-rc.0+2993be8

[root@cnfdd3-installer ~]# oc get node
NAME                                             STATUS   ROLES    AGE     VERSION
dhcp19-17-102.clus2.t5g.lab.eng.bos.redhat.com   Ready    master   41m     v1.21.0-rc.0+2993be8
dhcp19-17-113.clus2.t5g.lab.eng.bos.redhat.com   Ready    worker   5m18s   v1.21.0-rc.0+2993be8
dhcp19-17-118.clus2.t5g.lab.eng.bos.redhat.com   Ready    master   41m     v1.21.0-rc.0+2993be8
localhost                                        Ready    master   37m     v1.21.0-rc.0+2993be8

Comment 5 Michael Gourin 2021-04-20 14:39:14 UTC
I also have the same bug.

[root@cnfdt08-installer ~]# openshift-baremetal-install version
openshift-baremetal-install 4.8.0-0.nightly-2021-04-19-071934


[root@cnfdt08-installer ~]# oc get node
NAME                                  STATUS   ROLES            AGE   VERSION
dhcp-55-218.lab.eng.tlv2.redhat.com   Ready    master,virtual   22h   v1.21.0-rc.0+2993be8
localhost                             Ready    master,virtual   22h   v1.21.0-rc.0+2993be8


I've attached the log from the bootstrap VM.

Comment 6 Michael Gourin 2021-04-20 14:51:04 UTC
The file was too big to attach, so here's a link to it in my GDrive.

https://drive.google.com/file/d/1opSWj8Aet1i3bSE4ltt6sm75fFKUeXQa/view?usp=sharing

Comment 7 Arda Guclu 2021-04-20 16:18:00 UTC

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

Comment 8 Ben Nemec 2021-04-20 16:19:12 UTC
This is the same bug as the 4.7 one. The fix is still in review, which is why you're still seeing the problem. This should go away once the fix merges.


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