This is a known issue and no solution, just a workaround to as follow.
To work around this issue, VMware recommends to prepare a VM template running an Ubuntu Guest OS with an empty /etc/machine-id.
Clone your VM template to a new VM.
Power on the new VM and run these commands inside the Linux Guest OS:
echo -n > /etc/machine-id
rm /var/lib/dbus/machine-id
ln -s /etc/machine-id /var/lib/dbus/machine-id
Re-clone the new VM to a new VM template.
Alternatively, prepare a VM template explicitly setting the dhcp client identifier to mac.
Example 1: set the “dhcp-identifier: mac” in the /etc/netplan/*.yaml file as below:
network:
version: 2
renderer: networkd
ethernets:
default:
match:
name: e*
dhcp4: yes
dhcp-identifier: mac
Example 2: set the “ClientIdentifier=mac” in the /etc/systemd/network/default.network file.