| 2019-06-20 22:02:46 |
Maher AlAsfar |
bug |
|
|
added bug |
| 2019-06-20 22:03:08 |
Maher AlAsfar |
tags |
|
vmware |
|
| 2019-06-20 22:04:43 |
Maher AlAsfar |
tags |
vmware |
cloud-init vmware |
|
| 2019-06-20 22:04:55 |
Maher AlAsfar |
tags |
cloud-init vmware |
cloud-init customization vmware |
|
| 2019-06-20 22:12:28 |
Maher AlAsfar |
description |
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
- 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.
Result
the server is deployed from the template to vSphere and 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
Problem
Configuring the automation tool to use Static IP Range instead and vCenter Customization Specification 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, an updated hostname and connected network but .. Cloud-init fails to execute the cloud config code
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.
thank you.
Maher |
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 |
|
| 2019-06-21 14:30:08 |
Ryan Harper |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2019-06-21 14:30:08 |
Ryan Harper |
cloud-init (Ubuntu): status |
New |
Incomplete |
|
| 2019-06-21 14:45:45 |
Maher AlAsfar |
description |
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 |
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.
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 |
|
| 2019-06-21 14:46:18 |
Maher AlAsfar |
description |
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.
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 |
Hello,
I yet to find an answer and i know there has been many bugs reported in 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 |
|
| 2019-06-21 15:42:14 |
Maher AlAsfar |
attachment added |
|
DB_VM Cloud-init Log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5272129/+files/cloud-init.tar.gz |
|
| 2019-07-03 21:31:55 |
Maher AlAsfar |
attachment added |
|
cloud-init.tar.gz https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5274953/+files/cloud-init.tar.gz |
|
| 2019-07-04 15:56:02 |
Maher AlAsfar |
attachment added |
|
cloud-init.tar.gz https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5275077/+files/cloud-init.tar.gz |
|
| 2019-07-09 03:15:54 |
Maher AlAsfar |
attachment added |
|
Final Log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5275746/+files/Final-cloud-init.tar.gz |
|
| 2019-07-09 03:16:44 |
Maher AlAsfar |
attachment removed |
DB_VM Cloud-init Log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5272129/+files/cloud-init.tar.gz |
|
|
| 2019-07-09 03:16:56 |
Maher AlAsfar |
attachment removed |
cloud-init.tar.gz https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5274953/+files/cloud-init.tar.gz |
|
|
| 2019-07-09 03:17:09 |
Maher AlAsfar |
attachment removed |
cloud-init.tar.gz https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+attachment/5275077/+files/cloud-init.tar.gz |
|
|
| 2019-07-12 23:12:50 |
Maher AlAsfar |
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 |
|
| 2019-07-15 20:37:34 |
Joshua Powers |
bug |
|
|
added subscriber Joshua Powers |
| 2019-09-14 04:17:33 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Incomplete |
Expired |
|
