1990369 – remote worker added to cluster as localhost.localdomain

Bug 1990369 - remote worker added to cluster as localhost.localdomain

Summary: remote worker added to cluster as localhost.localdomain

Keywords:
Status:	CLOSED DUPLICATE of bug 1929160
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Networking
Sub Component:
Version:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Priority:	medium
Severity:	medium
Target Milestone:	---
Target Release:	---
Assignee:	Ben Nemec
QA Contact:	Victor Voronkov
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2021-08-05 09:35 UTC by Victor Voronkov
Modified:	2021-10-14 14:40 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2021-10-14 14:40:42 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Victor Voronkov 2021-08-05 09:35:08 UTC

Description of problem:
remote worker added to cluster as localhost.localdomain

Version-Release number of selected component (if applicable):
4.6.41

How reproducible:
Deploy OCP IPI BM regular cluster with 3 masters and 2 workers and add remote worker from different subnet

Steps to Reproduce:
1.
2.
3.

Actual results:
worker appear as localhost.localdomain while bnh shows rwn-0-0:

[kni@provisionhost-0-0 ~]$ oc get baremetalhost -n openshift-machine-api
NAME                   STATUS   PROVISIONING STATUS      CONSUMER                                  BMC                                                                                                 HARDWARE PROFILE   ONLINE   ERROR
openshift-master-0-0   OK       externally provisioned   ocp-edge-cluster-0-29dtb-master-0         redfish-virtualmedia://192.168.123.1:8000/redfish/v1/Systems/6f42c6c3-63aa-45ca-bb94-38716b92b53d                      true     
openshift-master-0-1   OK       externally provisioned   ocp-edge-cluster-0-29dtb-master-1         redfish-virtualmedia://192.168.123.1:8000/redfish/v1/Systems/b2bf4f03-10b6-4415-9c18-0827073b2056                      true     
openshift-master-0-2   OK       externally provisioned   ocp-edge-cluster-0-29dtb-master-2         redfish-virtualmedia://192.168.123.1:8000/redfish/v1/Systems/3447e792-36f7-4bc2-b252-6bbf9a06d1a9                      true     
openshift-rwn-0-0      OK       provisioned              ocp-edge-cluster-0-29dtb-worker-0-nwpqz   redfish-virtualmedia://192.168.123.1:8000/redfish/v1/Systems/4eec3688-91f4-4f04-aaf3-708a0144e50a   unknown            true     
openshift-worker-0-0   OK       provisioned              ocp-edge-cluster-0-29dtb-worker-0-26q8b   redfish-virtualmedia://192.168.123.1:8000/redfish/v1/Systems/140d43a8-c073-44b0-bbf5-cb3c81357889   unknown            true     
openshift-worker-0-1   OK       provisioned              ocp-edge-cluster-0-29dtb-worker-0-86v49   redfish-virtualmedia://192.168.123.1:8000/redfish/v1/Systems/40f4cf1e-545f-4bca-8854-750ee65d05b9   unknown            true     
[kni@provisionhost-0-0 ~]$ ^C
[kni@provisionhost-0-0 ~]$ oc get nodes -o wide
NAME                    STATUS   ROLES    AGE   VERSION           INTERNAL-IP       EXTERNAL-IP   OS-IMAGE                                                       KERNEL-VERSION                 CONTAINER-RUNTIME
localhost.localdomain   Ready    worker   17h   v1.19.0+4c3480d   192.168.128.122   <none>        Red Hat Enterprise Linux CoreOS 46.82.202107210110-0 (Ootpa)   4.18.0-193.60.2.el8_2.x86_64   cri-o://1.19.3-4.rhaos4.6.gitda07658.el8
master-0-0              Ready    master   2d    v1.19.0+4c3480d   192.168.123.112   <none>        Red Hat Enterprise Linux CoreOS 46.82.202107210110-0 (Ootpa)   4.18.0-193.60.2.el8_2.x86_64   cri-o://1.19.3-4.rhaos4.6.gitda07658.el8
master-0-1              Ready    master   2d    v1.19.0+4c3480d   192.168.123.109   <none>        Red Hat Enterprise Linux CoreOS 46.82.202107210110-0 (Ootpa)   4.18.0-193.60.2.el8_2.x86_64   cri-o://1.19.3-4.rhaos4.6.gitda07658.el8
master-0-2              Ready    master   2d    v1.19.0+4c3480d   192.168.123.137   <none>        Red Hat Enterprise Linux CoreOS 46.82.202107210110-0 (Ootpa)   4.18.0-193.60.2.el8_2.x86_64   cri-o://1.19.3-4.rhaos4.6.gitda07658.el8
worker-0-0              Ready    worker   47h   v1.19.0+4c3480d   192.168.123.135   <none>        Red Hat Enterprise Linux CoreOS 46.82.202107210110-0 (Ootpa)   4.18.0-193.60.2.el8_2.x86_64   cri-o://1.19.3-4.rhaos4.6.gitda07658.el8
worker-0-1              Ready    worker   47h   v1.19.0+4c3480d   192.168.123.130   <none>        Red Hat Enterprise Linux CoreOS 46.82.202107210110-0 (Ootpa)   4.18.0-193.60.2.el8_2.x86_64   cri-o://1.19.3-4.rhaos4.6.gitda07658.el8

Comment 1 Ben Nemec 2021-08-05 20:18:08 UTC

After looking at this environment, I think this is probably the same as https://bugzilla.redhat.com/show_bug.cgi?id=1990369. The RWN node's DHCP record doesn't include a hostname, and there's a known race in using hostnames from rDNS right now. We're waiting on a new feature from NetworkManager to show up in our images in order to fix the problem.

Comment 2 Ben Nemec 2021-08-31 17:40:31 UTC

I seem to have messed up the link in my previous comment. It should be https://bugzilla.redhat.com/show_bug.cgi?id=1929160.

Comment 3 Ben Nemec 2021-10-14 14:40:42 UTC

I'm going to duplicate this while we wait for verification on the other bug. Feel free to reopen if it turns out to be a different issue.

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

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