When trying to add the worker node to the existing TKGM cluster VM on vsphere was created but the status of machine resource is in Not ready state.
devmsbootstrap:~/work/uwatsu/node-pool$ kubectl get vspheremachine -n default
NAME CLUSTER READY PROVIDERID
dev-01 tkg-01 true vsphere://UUID 173d
dev-01 tkg-01 14m ------ > machine getting deployed but not ready
/var/log/syslog
Dec 12 04:26:20 testcluster-: Selected source 10.x.x.x
Dec 12 04:26:20 testcluster-: System clock wrong by 93.302195 seconds, adjustment started
Dec 12 04:26:20 testcluster-- System clock was stepped by 93.302195 seconds
TKGM 2.5.x
Time difference between the management cluster and workload cluster due to known issue with Ubuntu 22.04 OVA when DHCP is used for time sync.
Run below command both on management cluster and workload cluster to check time difference.
root@mgmtclsuter :~# chronyc sources
This is a known issue with Ubuntu 22.04 & currently there is no permanent fix.
Workaround:
Provide the IP of NTP on /etc/chrony/chrony.conf manually
root@dev-md-1:~# cat /etc/chrony/chrony.conf
# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usable directives.
# Include configuration files found in /etc/chrony/conf.d.
confdir /etc/chrony/conf.d
# This will use (up to):
# - 4 sources from ntp.ubuntu.com which some are ipv6 enabled
# - 2 sources from 2.ubuntu.pool.ntp.org which is ipv6 enabled as well
# - 1 source from [01].ubuntu.pool.ntp.org each (ipv4 only atm)
# This means by default, up to 6 dual-stack and up to 2 additional IPv4-only
# sources will be used.
# At the same time it retains some protection against one of the entries being
# down (compare to just using one of the lines). See (LP: #1754358) for the
# discussion.
#
# About using servers from the NTP Pool Project in general see (LP: #104525).
# Approved by Ubuntu Technical Board on 2011-02-08.
# See http://www.pool.ntp.org/join.html for more information.
pool 10.x.x.x iburst maxsources 4 maxpoll 16 -----------> Added NTP server IP manually