[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
I have Setup the cloud-init as the customization engine, based on this KB [2] instead which is similar to above mentioned KB [1] but it with two extra steps Item 3 and 4. i also made sure i have removed the After=Dbus.service [2] https://kb.vmware.com/s/article/54986 The result is i see Customization event happening and successful in the VM Event ( so the VM still rebooted, is that Expected even though we configured cloud-init to be the customization engine? ), Network connected, Static IP provided and hostname updated but none of the userdata Cloud config made it through like for example installing mysql-server package. at this point i m confident there is no solution here for cloud-init to work on VMware unless someone else tells me otherwise. i will be more focused on introducing Ansible open source to deliver packages , etc and remove cloud-init completely from the template -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Thanks Joshua .. thats pretty much it yes So if i need to use Cloud Config / User data to execute scripts i must use cloud-init as well to do the customizization instead of using Perl ( VMware Customization ) baed on the provided KB [1]. The problem is when i do that i have no network, no IP, no updated hostname and of course no connectivity for anything to work. what i also noticed is anytime i m using Staic IP during the provisioing from the automation too it triggers a VMware Customization, i don't even have to specify a customization Specification in vCenter for it to kick that off. [1] https://kb.vmware.com/s/article/59557?lang=en_US -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Thanks Joshua .. thats pretty much it. so at all times if i need to use Cloud Config / User data i must use cloud-init as well to do the customize instead of Perl . the problem is when i do that i have no network, no IP, no updated hostname update and of course no connectivity for anything to work. unless we are saying that currently we can't use Cloud-init on VMware period ? -- 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
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
anyone can look at the logs i provided.. here we have a successful customization where the VM gets IP-ed , hostname is updated after the customization reboot. the problem now is that Cloud-init execute i think before the reboot when there is no network .. please if you have the time . take a look at the log provided or recommend a workaround where it forces cloud-init to execute after the customization .. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Just tested Ubuntu 18.04 ( same issue ) logs attached Behaviour for deploying Ubuntu 18 VMs using Static IP from Automation tool Automation tool maps an image iso to pass cloud-init user data Template work done -- Deploy Ubuntu 18.04 from iso sudo apt-get udpate && sudo apt-get upgrade Cloud-init installed by default following KB https://kb.vmware.com/s/article/56409 But used After=dbus.socket instead of After=dbus.service sudo cloud-init clean --log Open-VM-Tools 10346 (10.3.10) Compatibility: ESXi 6.7 Update 2 and later (VM version 15) for the VM Hardware Tasks Invoked by vCenter when profivsioning from CAS - Clone Virtual Machine from Template - Reconfigure Virutal Machine - Customize Virutal Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start and successful, listed in the VM Events - VM reboots and the network now is connected - IP provied from Static IP Range - Hostname is Updated - Cloud config code fail to executes i have attached the logs. not sure if this ever going to work .. ** Attachment added: "Maher's Ubuntu 18.04 logs" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5276845/+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
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
@Pengpeng Sun (pengpengs) Just tested Ubuntu 18.04 ( same issue ) logs attached Behaviour for deploying Ubuntu 18 VMs using Static IP from Automation tool Automation tool maps an image iso to pass cloud-init user data Template work done -- Deploy Ubuntu 18.04 from iso sudo apt-get udpate && sudo apt-get upgrade Cloud-init installed by default following KB https://kb.vmware.com/s/article/56409 But used After=dbus.socket instead of After=dbus.service sudo cloud-init clean --log Open-VM-Tools 10346 (10.3.10) Compatibility: ESXi 6.7 Update 2 and later (VM version 15) for the VM Hardware Tasks Invoked by vCenter when profivsioning from CAS - Clone Virtual Machine from Template - Reconfigure Virutal Machine - Customize Virutal Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start and successful, listed in the VM Events - VM reboots and the network now is connected - IP provied from Static IP Range - Hostname is Updated - Cloud config code fail to executes in the right order i have attached the logs ** Attachment added: "Maher's Log for Ubuntu 18.04" https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715/+attachment/5276830/+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/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Hi @Pengpeng Sun (pengpengs) This is where i am with Ubuntu 16.04 Behaviour for deploying Ubuntu 16.04 VMs using Static IP from Automation tool After installing cloud-init Template Tasks Taken Deploy Ubuntu 16.04 from ISO sudo apt-get update && sudo apt-get upgrade sudo apt-get install cloud-init sudo dpkg-reconfigure cloud-init -> Selecting only OVF and NONE as data sources. since the automation tool maps an iso image to pass the user data to cloud-init Following KB https://kb.vmware.com/s/article/59687 But using After=dbus.socket instead of After=dbus.service Using Open-VM-Tools 10304 (10.2.0) Using ESXi 6.7 Update 2 and later (VM version 15) for the VM Hardware Tasks Invoked by vCenter when provisioning from Automation tool === Clone Virtual Machine from Template Reconfigure Virutal Machine Customize Virutal Machine Guest OS Power on Virtual Machine During the boot time the network state is disconnected Customization does start and successful, listed in the VM Events VM reboots and the network shows as connected IP provied from Static IP Range Hostname is Updated Cloud config fail to executes in the right order ( Before Network Settings are Applied ) most of the time but magically sometimes it does execute fine after the network is up When it doesn't work, looking at the cloud-init logs that Cloud-init start way too early when the network isn't setup / started yet when it executes. Looking for a way to make cloud-init executes after VMware Customization .. i thought the KB i mentioned above would do that but it only help getting the customization to complete successfully because if you don't add the After=dbus.socket to the open-vm-tools.service , everything else fails which is way worse since the network will be never connected and the customization will error out in the VM Events where the logs shows the same exact error mentioned in the KB above. Ofcourse this has a completely different dynamics when your testing with Ubuntu 18.04 which i will get into once i figure Ubuntu 16.04 out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822204] Re: open-vm-tools 10.3.10 released
folks how can i update to open-vm-tools 10.3.10 ... when installing Ubuntu i only get version 10.2.0 and there is no online updates thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822204 Title: open-vm-tools 10.3.10 released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1822204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Folks like so far until someone says otherwise there using a static IP when provisioning a VM on vSphere from a template that includes cloud- init just doesn't work.. is anyone open to have a WebEx/zoom session to look into maybe understanding why this is still an issue. i have tried open-vm-tools vs VMware tools . i have tried After=dbus.service vs After=dbus.socket and this is just around Ubuntu 16.04 because with 18.04 and above its a whole different experience of its not working either. even other distros. Thanks.. -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Hi Ryan Can you please check the logs for this.. this a rising issue that is happen quite often from customers i have dealt with. Configuration === VMs to be provisioned on vSphere 6.7 U2 template is Ubuntu 16.04.6 LTS with Cloud-init 19.1 and Open-vm-tools 10304 (10.2.0) sudo dpkg-reconfigure cloud-init and selected OVF and NONE /lib/systemd/system/Open-vm-tools.service Contain: [Unit] Description=Service for virtual machines hosted on VMware Documentation=http://open-vm-tools.sourceforge.net/about.php ConditionVirtualization=vmware DefaultDependencies=no Before=cloud-init-local.service After=local-fs.target After=dbus.socket [Service] ExecStart=/usr/bin/vmtoolsd TimeoutStopSec=5 [Install] WantedBy=multi-user.target Cloud Config Code contain : cloudConfig: | #cloud-config repo_update: true repo_upgrade: all packages: - mysql-server ran sudo cloud-init clean --log before converting to a template. Result === Tasks Invoked by vCenter when provisioning by the automation tool from the prepared template - Clone Virtual Machine from Template - Reconfigure Virutal Machine - Customize Virutal Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected Waits 5 min on A start job is running for Raise network interfaces during post then continues to boot - VMware Customization starts and successful, listed in the VM Events in vCenter - VM reboots and the network shows as connected now - IP provied from Static IP Range - Hostname is Updated - Cloud config fails to execute in the right order at it seems it ran when there was no network connectivity and before the vmware customization to finish. Note: No vCenter Customization Specification used here. Logs attached can you provide any recommendation on how to fix this or if you can confirm if its a bug today. i m really trying here and i just need a little support thank you ** Attachment added: "Final Log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5275746/+files/Final-cloud-init.tar.gz ** Attachment removed: "DB_VM Cloud-init Log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5272129/+files/cloud-init.tar.gz ** Attachment removed: "cloud-init.tar.gz" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5274953/+files/cloud-init.tar.gz ** Attachment removed: "cloud-init.tar.gz" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5275077/+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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
This isn't going anywhere, nor getting any help .. please close the bug -- 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
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
I have been spending so many cycle on this, here are the Testing Tasks around Ubuntu 16.04 Customization with Cloud-init and its expected behaviour for vSphere Provisioning Using After=dbus.socket doesn't work so stick the KB i mentioned below if you want to do it yourself its Test 2 with DHCP and Test 4 for Static IP Please let me know if you were successful or have any comments, questions or suggestions - - Create an Ubuntu 16.04 Virtual Machine on vSphere 6.7 U2. - Apply the latest updates and upgrades -> sudo apt-get update && sudo apt-get upgrades Environment Facts - DHCP is available on the network when preparing the template and later for provisioning. - Cloud Assembly Static IP range also available for vSphere deployments. Test 1 === behavior for deploying VMs using DHCP from CAS before installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is Disconnected - Customization Starts and Succeeds, listed in the VM Events - VM Reboots During the boot time the network state is Connected - IP provided from DHCP - Host-name Updated Note: No Customization Specification used here. Test 2 == behavior for deploying VMs using DHCP from CAS After installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is Connected - Customization doesn't Start at all, so its not listed in the VM Events - IP provided from DHCP - Host-name is not Updated - Cloud Config Code executes successfully Note: No Customization Specification used here. Test 3 == behavior for deploying VMs using Static IP from CAS before installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start, listed in the VM Events and successful - VM reboots and network shows as connected - IP provided from Static IP Range - Host-name is Updated Note: No Customization Specification used here. Test 4 == behavior for deploying VMs using Static IP from CAS After installing cloud-init following KB https://kb.vmware.com/s/article/59687 Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start and successful, listed in the VM Events - VM reboots and the network shows as connected - IP provided from Static IP Range - Host-name is Updated - Cloud config executes fine Note: No Customization Specification used here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
I have been spending so many cycle on this, here are the Testing Tasks around Ubuntu 16.04 Customization with Cloud-init on vSphere and its expected behaviour - - Create an Ubuntu 16.04 Virtual Machine on vSphere 6.7 U2. - Apply the latest updates and upgrades -> sudo apt-get update && sudo apt-get upgrades Environment Facts - DHCP is available on the network when preparing the template and later for provisioning. - Cloud Assembly Static IP range also available for vSphere deployments. Test 1 === behavior for deploying VMs using DHCP from CAS before installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is Disconnected - Customization Starts and Succeeds, listed in the VM Events - VM Reboots During the boot time the network state is Connected - IP provided from DHCP - Host-name Updated Note: No Customization Specification used here. Test 2 == behavior for deploying VMs using DHCP from CAS After installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is Connected - Customization doesn't Start at all, so its not listed in the VM Events - IP provided from DHCP - Host-name is not Updated - Cloud Config Code executes successfully Note: No Customization Specification used here. Test 3 == behavior for deploying VMs using Static IP from CAS before installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start, listed in the VM Events and successful - VM reboots and network shows as connected - IP provided from Static IP Range - Host-name is Updated Note: No Customization Specification used here. Test 4 == behavior for deploying VMs using Static IP from CAS After installing cloud-init following KB https://kb.vmware.com/s/article/59687 Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start and successful, listed in the VM Events - VM reboots and the network shows as connected - IP provided from Static IP Range - Host-name is Updated - Cloud config executes fine Note: No Customization Specification used here. -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Anyone i can work with live via a WebEx / zoom session on this, dedicated a couple of hours please email me at maheralas...@gmail.com and i ll send you an invite .. i just think this way its much a faster way to troubleshoot this and get to a resolution -- 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
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
what's the update on this as this continue to be an issue for customers using Ubuntu and cloud-init on vmware ? have we like reached a solution in terms of outlining the steps needed to be done for this to work ? Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Test 14 Using DHCP 1- Install a fresh Ubuntu 16.04 Server 2- run sudo apt update && sudo apt upgrade 3- install Cloud init 4- if any delete /var/log/cloud-ini* from the VM before shutting it down and converting it to a template 5- run dpkg-reconfigure cloud-init and only select OVF only. 6- run cloud-init clean --logs 7- shutdown the VM and convert to template 8- provision a VM using DHCP from the template Result - Ubuntu 16.04 provisioned - Network connected - Ip provided from DHCP - Hostname is not updated as Customization isn't triggered <-- Problem 1 - Cloud config Code was deployed successfully -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Anyone can take a look .. if there was a training class for cloud-init online i would take it. documentation also doesn't talk about the process flow or show end to end examples. just cloud config syntax example. its like here the code go figure it out!! very frustrating. -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Another approach i followed. is https://kb.vmware.com/s/article/59557 where i m disabling guest customization with cloud-init - Ubuntu 16.04 provisioned - Network connected - Ip provided from DHCP - Hostname was updated this time - Cloud config code wasn't deployed <--- Problem logs attached. ** Attachment added: "cloud-init.tar.gz" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5275077/+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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Any Luck on the 2nd log collection based on what i followed in Step #9 -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Hi Ryan With the automation tool we are using we are passing the cloud config user data information via an attached ISO via the vm CD-ROM .. should using dpkg-reconfigure cloud-init command to select only OVF as a data source should be enough in this case since we are only provision to VMware vSphere? or do i need to select all available data sources and not really touch that ? -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
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. -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
i guessing based on https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715 i can't really disable cloud-init cause i need to execute the cloud config code that I'm pushing when i m provisioning the VM.. this leaves me that i need to set cloud-init to do the customization here . Correct ? -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
hi Ryan . thank you for taking the time. this is a VMware Ubuntu 16.04 VM that later used as a template where we installed cloud-init top . as we prepare the template we do reboot the VM after .. i normally delete the cloud-init* logs from /var/log and maybe i didn't here... unless there is a clean up process that need to be followed after install cloud-init that i didnt do. once the template is ready users can deploy VMs from this standard Template now... when they do machine customization happens on first boot and i m guessing that's when cloud-init start executing but due to the customization the machine does reboot .. would this explain what's your seeing in the logs. is there a way we can delay cloud-init from executing until for example the next reboot .. or somehow build some kind of dependency that it execute after the VM customization process ? -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Anyone else can help with this we are trying to make cloud-init work when provisioning a ubuntu 16 on a sphere. -- 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
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;"
** Attachment added: "DB_VM Cloud-init Log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5272129/+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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
** 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. + I yet to find an answer and i know there has been 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 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 + - Using DHCP Result 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 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 we also tried the suggestion mentioned in a pervious bug here 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 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 ** Description changed: Hello, I yet to find an answer and i know there has been many bugs reported in - the past and i really need to know what we need to do to get this to - work. + the past around this issue and i really need to know what we need to do + to get this to work, so here it is : Situation An automation tool is used to provision Ubuntu 16 VMs to vSphere/ESXi 6.7 U2 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, 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 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 we also tried the suggestion mentioned in a pervious bug here 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 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
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
** 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
[Bug 1833623] [NEW] VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Public bug reported: 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 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, 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 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 we also tried the suggestion mentioned in a pervious bug here 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 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 ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: cloud-init customization vmware ** Tags added: vmware ** Tags added: cloud-init ** Tags added: customization -- 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
