Comment 2 for bug 1833623

Sure thing! Attached

thank you for looking into this

this is a two machine deployment of Wordpress from an ubuntu 16.04 templated. Web and DB VMs . the tar ball is from the DB machine using a static IP Range for connectivity and the setting mentioned in the https://kb.vmware.com/s/article/56409 without Customization Specification that fact that Static IP force customization on the vSphere side.

Result

1- When the Server is deployed and boots it takes 5 min waiting on the A Start job is running for Raise network interfaces
2. After that it says it Failed to start Raise network Interface and continues to boot
3. Machines reboot and we see successful customization in the VM Event. Host name gets updated , machine gets IP from Static IP and boots really fast the 2nd time
4. Cloud-init Cloud Config Code below never makes it. i m guess to the fact that the machine rebooted and had no connectivity before that for cloud-init to execute which explains maybe why it works in DHCP without cutomization.

Cloud Config Code in question

#cloud-config
        repo_update: true
        repo_upgrade: all

        packages:
         - mysql-server

        runcmd:
         - sed -e '/bind-address/ s/^#*/#/' -i /etc/mysql/mysql.conf.d/mysqld.cnf
         - service mysql restart
         - mysql -e "GRANT ALL PRIVILEGES ON *.* TO '${input.username}'@'%' IDENTIFIED BY '${input.userpassword}';"
         - mysql -e "FLUSH PRIVILEGES;"