Bug 1855877 - [4.5.z] Network Dispatcher long hostname character count is incorrect
Summary: [4.5.z] Network Dispatcher long hostname character count is incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.5.z
Assignee: Ben Howard
QA Contact: Michael Nguyen
URL:
Whiteboard: coreos
: 1850774 1854436 (view as bug list)
Depends On: 1853584
Blocks: 1186913 1855878
TreeView+ depends on / blocked
 
Reported: 2020-07-10 19:29 UTC by Micah Abbott
Modified: 2023-10-06 21:03 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1853584
: 1855878 (view as bug list)
Environment:
Last Closed: 2020-07-30 18:56:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 1939 0 None closed [release 4.5] Bug 1855877: cherry-pick hostname fixes 2021-01-26 16:06:31 UTC
Red Hat Product Errata RHBA-2020:3028 0 None None None 2020-07-30 18:57:33 UTC

Comment 1 Ben Howard 2020-07-10 19:44:16 UTC
*** Bug 1854436 has been marked as a duplicate of this bug. ***

Comment 2 Ben Howard 2020-07-10 19:48:01 UTC
*** Bug 1850774 has been marked as a duplicate of this bug. ***

Comment 6 Michael Nguyen 2020-07-27 15:26:32 UTC
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-07-25-031342   True        False         39m     Cluster version is 4.5.0-0.nightly-2020-07-25-031342

$ oc get node
NAME                                       STATUS   ROLES    AGE   VERSION
yunjiang00123456789-4pmb8-master-0         Ready    master   57m   v1.18.3+012b3ec
yunjiang00123456789-4pmb8-master-1         Ready    master   57m   v1.18.3+012b3ec
yunjiang00123456789-4pmb8-master-2         Ready    master   57m   v1.18.3+012b3ec
yunjiang00123456789-4pmb8-worker-a-bzgzg   Ready    worker   26m   v1.18.3+012b3ec
yunjiang00123456789-4pmb8-worker-b-gv47k   Ready    worker   26m   v1.18.3+012b3ec
yunjiang00123456789-4pmb8-worker-c-dfqkw   Ready    worker   26m   v1.18.3+012b3ec
$ oc debug node/yunjiang00123456789-4pmb8-worker-a-bzgzg
Starting pod/yunjiang00123456789-4pmb8-worker-a-bzgzg-debug ...
To use host binaries, run `chroot /host`

If you don't see a command prompt, try pressing enter.

sh-4.2# chroot /host
sh-4.4# journalctl -u node-valid-hostname.service

-- Logs begin at Mon 2020-07-27 14:30:57 UTC, end at Mon 2020-07-27 15:07:01 UTC. --
Jul 27 14:36:54 yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-c systemd[1]: Starting Ensure the node hostname is valid for the cluster...
Jul 27 14:36:54 yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-c systemd[1]: Started Ensure the node hostname is valid for the cluster.
Jul 27 14:37:47 yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-c systemd[1]: Stopped Ensure the node hostname is valid for the cluster.
Jul 27 14:37:47 yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-c systemd[1]: node-valid-hostname.service: Consumed 0 CPU time
-- Reboot --
Jul 27 14:38:15 localhost systemd[1]: Starting Ensure the node hostname is valid for the cluster...
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Started Ensure the node hostname is valid for the cluster.
sh-4.4# journalctl --no-pager | grep -20 "using trunacated hostname"
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0658] dhcp4 (ens4): option rfc3442_classless_static_routes => '10.0.32.1/32 0.0.0.0 0.0.0.0/0 10.0.32.1'
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0658] dhcp4 (ens4): option routers              => '10.0.32.1'
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0658] dhcp4 (ens4): option subnet_mask          => '255.255.255.255'
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0658] dhcp4 (ens4): state changed unknown -> bound
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0680] device (ens4): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0722] device (ens4): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0728] device (ens4): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0733] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0745] manager: NetworkManager state is now CONNECTED_SITE
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0747] policy: set 'Wired connection 1' (ens4) as default for IPv4 routing and DNS
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0749] policy: set-hostname: set hostname to 'yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-ci.internal' (from DHCPv4)
Jul 27 14:38:16 localhost dbus-daemon[1280]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=1284 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Jul 27 14:38:16 localhost dbus-daemon[1280]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0807] device (ens4): Activation: successful, device activated.
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0817] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 27 14:38:16 localhost NetworkManager[1284]: <info>  [1595860696.0826] manager: startup complete
Jul 27 14:38:16 localhost NetworkManager[1284]: <warn>  [1595860696.0831] hostname: couldn't set the system hostname to 'yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-ci.internal' using hostnamed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid hostname 'yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-ci.internal'
Jul 27 14:38:16 localhost NetworkManager[1284]: <warn>  [1595860696.0831] policy: set-hostname: couldn't set the system hostname to 'yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-ci.internal': (1) Operation not permitted
Jul 27 14:38:16 localhost NetworkManager[1284]: <warn>  [1595860696.0831] policy: set-hostname: you should use hostnamed when systemd hardening is in effect!
Jul 27 14:38:16 localhost systemd[1]: Started Network Manager Wait Online.
Jul 27 14:38:16 localhost 90-long-hostname[1424]: yunjiang00123456789-4pmb8-worker-a-bzgzg.c.openshift-gce-devel-ci.internal is longer than 63 characters, using trunacated hostname
Jul 27 14:38:16 localhost 90-long-hostname[1426]: setting transient hostname to yunjiang00123456789-4pmb8-worker-a-bzgzg
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd-hostnamed[1315]: Changed host name to 'yunjiang00123456789-4pmb8-worker-a-bzgzg'
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg bash[1432]: node identified as yunjiang00123456789-4pmb8-worker-a-bzgzg
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Started Ensure the node hostname is valid for the cluster.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Reached target Network is Online.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Starting OpenSSH server daemon...
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Starting CRI-O Auto Update Script...
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Starting Generate /run/issue.d/console-login-helper-messages.issue...
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg sshd[1434]: Server listening on 0.0.0.0 port 22.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg sshd[1434]: Server listening on :: port 22.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Started OpenSSH server daemon.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Started Generate /run/issue.d/console-login-helper-messages.issue.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Starting RPC Bind...
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Starting Permit User Sessions...
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Started Permit User Sessions.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg systemd[1]: Started Getty on tty1.
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg rpc.statd[1458]: Version 2.3.3 starting
Jul 27 14:38:16 yunjiang00123456789-4pmb8-worker-a-bzgzg rpc.statd[1458]: Flags: TI-RPC
sh-4.4# hostname
yunjiang00123456789-4pmb8-worker-a-bzgzg
sh-4.4#

Comment 8 errata-xmlrpc 2020-07-30 18:56:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3028

Comment 9 Red Hat Bugzilla 2023-09-14 06:03:44 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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