Hi Ryan Based on the https://bugs.launchpad.net/ubuntu/+source/open-vm- tools/+bug/1793715 which is really was around Ubuntu 18.04
i did the following after installing a new ubuntu 16.04 and turning into a template 1- Install a fresh Ubuntu 16.04 Server 2- run sudo apt update && sudo apt upgrade 3- install Cloud init 4- set cloud-init as the customization engine Set “disable_vmware_customization: false" in "/etc/cloud/cloud.cfg" 5- Open the /usr/lib/tmpfiles.d/tmp.conf file. Go to the line 11 and add the prefix #. or example: #D /tmp 1777 root root - 6- If you have open-vm-tools installed, open the /lib/systemd/system/open-vm-tools.service file. Add “After=dbus.service” under [Unit]. later the bug link you outlined they mention they actually want you to use After=dbus.socket instead so thats what i used. 7- if any delete /var/log/cloud-ini* from the VM before shutting it down and converting it to a template 8- run cloud-init clean --logs 9- shutdown the VM and convert to template 10- provision a VM using DHCP from the template Result - Ubuntu 16.04 provisioned - Network connected - Ip provided from DHCP - Hostname is not updated as it still uses the original template hostname. <-- Problem 1 - Cloud config code wasn't deployed <--- Problem 2 new log attached. ** Attachment added: "cloud-init.tar.gz" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5274953/+files/cloud-init.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833623 Title: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
