** Description changed: Hello, I yet to find an answer and i know there has many bugs reported in the past and i really need to know what we need to do to get this to work. Situation An automation tool is used to provision Ubuntu 16 VMs to vSphere/ESXi 6.7 U2 - Steps I Followed + Steps I Followed to setup my Ubuntu 16.04 template - Install fresh Ubuntu 16.04 Server - run sudo apt update && sudo apt upgrade - install Cloud init - run dpkg-reconfigure cloud-init and only select OVF, NoCloud and None as a datasource for vSphere to Speed up Boot time since its only targeted to be deployed on vSphere and not any public cloud. + - Using DHCP Result - the server is deployed from the template to vSphere and ends up with No + The server is deployed from the template to vSphere, ends-up with No Customization, No Hostname update, connected network via DHCP and Cloud- init executes the Cloud Config code that install an x app successfully - - + of course this is not the desired state. where we want customization for + security reasons and so the hostname to be updated Problem - Configuring the automation tool to use Static IP Range instead and - vCenter Customization Specification prevents the VMs of acquiring the IP + Configuring the automation tool to use Static IP Range and vCenter + Customization Specification instead prevents the VMs of acquiring the IP from the Static IP Range and the VM network ends up in a disconnected state which results in cloud-init failing to execute the cloud config code + Following https://kb.vmware.com/s/article/56409 fixes the + customization part where the VM gets the IP it needs from the Static IP + Range, gets an updated hostname and a connected network but .. Cloud- + init fails to execute the cloud config code - Following https://kb.vmware.com/s/article/56409 fixes the customization part where the VM gets the IP it needs from the Static IP Range, an updated hostname and connected network but .. Cloud-init fails to execute the cloud config code + we also tried the suggestion mentioned in a pervious bug here + https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715 - we also tried the suggestion mentioned in - https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715 and that is to use After=dbus.socket instead of After=dbus.service but the outcome was the same . works on the customization side but Cloud- init fails to execute the cloud config code. - looking for best approach here where the VM is customization handled by - vmware and Cloud Config code being handled by Cloud-init without a - conflict. so everyone is happy. + looking for best approach here where the VM customization is handled by + vmware and Cloud Config code execution being handled by Cloud-init + without a conflict. so everyone is happy. thank you. Maher
-- 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
