-
Bug
-
Resolution: Cannot Reproduce
-
Undefined
-
None
-
4.10.z
-
Important
-
No
-
Rejected
-
False
-
-
Customer Facing
-
-
Description of problem:
During introspection the hostname is successfully set:
Introspection results:
[core@localhost ~]$ hostname nlhen06st3om003.test.ci.internal.vodafone.nl [kni@NLHEN06ST3RM005 ~]$ ssh core@10.58.158.69 Red Hat Enterprise Linux CoreOS 410.84.202210040010-0 Part of OpenShift 4.10, 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.10/architecture/architecture-rhcos.html --- Last login: Fri Mar 24 08:57:07 2023 from 10.58.158.71 [systemd] Failed Units: 1 NetworkManager-wait-online.service [core@nlhen06st3om003 ~]$ exit
During the bootstrapping phase, the nodes don't receive a valid hostname with the PTR-lookup.
Bootstrapping results:
[core@localhost ~]$ journalctl |grep -i hostname Mar 24 09:06:33 localhost NetworkManager[2166]: <info> [1679648793.5157] hostname: hostname: hostnamed not used as proxy creation failed with: Could not connect: No such file or directory Mar 24 09:06:58 localhost ignition[2493]: INFO : files: createFilesystemsFiles: createFiles: op(26): [started] writing file "/sysroot/var/usrlocal/bin/mco-hostname" Mar 24 09:06:58 localhost ignition[2493]: INFO : files: createFilesystemsFiles: createFiles: op(26): [finished] writing file "/sysroot/var/usrlocal/bin/mco-hostname" Mar 24 09:07:02 localhost ignition[2493]: INFO : files: op(44): [started] processing unit "node-valid-hostname.service" Mar 24 09:07:02 localhost ignition[2493]: INFO : files: op(44): op(45): [started] writing unit "node-valid-hostname.service" at "/sysroot/etc/systemd/system/node-valid-hostname.service" Mar 24 09:07:02 localhost ignition[2493]: INFO : files: op(44): op(45): [finished] writing unit "node-valid-hostname.service" at "/sysroot/etc/systemd/system/node-valid-hostname.service" Mar 24 09:07:02 localhost ignition[2493]: INFO : files: op(44): [finished] processing unit "node-valid-hostname.service" Mar 24 09:07:05 localhost ignition[2493]: INFO : files: op(5d): [started] setting preset to enabled for "node-valid-hostname.service" Mar 24 09:07:05 localhost ignition[2493]: INFO : files: op(5d): [finished] setting preset to enabled for "node-valid-hostname.service" Mar 24 09:07:09 localhost coreos-teardown-initramfs[2657]: info: no initramfs hostname information to propagate Mar 24 09:07:11 localhost systemd[1]: /usr/lib/systemd/system/bootupd.service:22: Unknown lvalue 'ProtectHostname' in section 'Service' Mar 24 09:07:20 localhost ovs-vsctl[3625]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait add Open_vSwitch . external-ids hostname=localhost Mar 24 09:07:20 localhost ovs-vsctl[3704]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait add Open_vSwitch . external-ids hostname=localhost Mar 24 09:07:21 localhost dbus-daemon[3444]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.13' (uid=0 pid=3711 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0") Mar 24 09:07:21 localhost systemd[1]: Starting Hostname Service... Mar 24 09:07:21 localhost dbus-daemon[3444]: [system] Successfully activated service 'org.freedesktop.hostname1' Mar 24 09:07:21 localhost systemd[1]: Started Hostname Service. Mar 24 09:07:21 localhost NetworkManager[3711]: <info> [1679648841.1145] hostname: hostname: using hostnamed Mar 24 09:07:51 localhost systemd[1]: systemd-hostnamed.service: Succeeded. Mar 24 09:07:51 localhost systemd[1]: systemd-hostnamed.service: Consumed 42ms CPU time Mar 24 09:08:21 localhost systemd[1]: Starting Wait for a non-localhost hostname... Mar 24 09:08:21 localhost mco-hostname[4707]: waiting for non-localhost hostname to be assigned Mar 24 09:13:21 localhost systemd[1]: node-valid-hostname.service: start operation timed out. Terminating. Mar 24 09:13:21 localhost systemd[1]: node-valid-hostname.service: Main process exited, code=killed, status=15/TERM Mar 24 09:13:21 localhost systemd[1]: node-valid-hostname.service: Failed with result 'timeout'. Mar 24 09:13:21 localhost systemd[1]: Failed to start Wait for a non-localhost hostname. Mar 24 09:13:21 localhost systemd[1]: node-valid-hostname.service: Consumed 395ms CPU time Mar 24 09:13:21 localhost systemd[1]: /usr/lib/systemd/system/bootupd.service:22: Unknown lvalue 'ProtectHostname' in section 'Service'
The nodes can resolve the FQDN during a PTR-lookup:
[kni@NLHEN06ST3RM005 ~]$ ssh core@10.58.158.68 Red Hat Enterprise Linux CoreOS 410.84.202301302127-0 Part of OpenShift 4.10, 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.10/architecture/architecture-rhcos.html--- Last login: Fri Mar 24 09:21:02 2023 from 10.58.158.71 [systemd] Failed Units: 1 NetworkManager-wait-online.service [core@localhost ~]$ nslookup 10.58.158.68 68.158.58.10.in-addr.arpa name = nlhen06st3om002.test.ci.internal.vodafone.nl. Manually restarting the Networkmanager.service ensures the hostname gets set in the node: [core@localhost ~]$ sudo systemctl restart NetworkManager.service [core@localhost ~]$ hostname nlhen06st3om003.test.ci.internal.vodafone.nl
