Ubuntu
open-vm-tools package

Ubuntu 18 Nightly Builds are failing on Vmware Openstack because of Problems with Cloud Init/VMware Perl customization

Asked by Matti Haack on 2019-03-04

Hello,

as confirmed with vmware, it seems that there is a issue with guest OS Customization/open-vmware-tools and cloud init:
https://kb.vmware.com/s/article/59754

When cloning a Ubuntu 18 VM in Vmware Integrated Openstack, the deployment fails, as the Machine is not getting configured correctly by cloud init or vmware tools

Is there any plan to install the workaround as described here: https://kb.vmware.com/s/article/54986
to the Nightly Builds?

With best regards
 Matti Haack

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu open-vm-tools Edit question
Assignee:
No assignee Edit question
Solved by:
Matti Haack
Solved:
2019-03-06
Last query:
2019-03-06
Last reply:
2019-03-04
actionparsnip (andrew-woodhead666) said : #1

There is no "Ubuntu 18". There is Ubuntu 18.04 (Codenamed "Bionic" and is LTS (Supported 5 years)) and Ubuntu 18.10 (Codenamed "Cosmic" and is not LTS).

Which are you using please? If you are unsure then please give the output of:

uname -a; lsb_release -a

Thanks

Matti Haack (matttih) said : #2

Sorry to be so vague.

The problem exists at least with the cloud image from Ubuntu 18.04

https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img

Matti Haack (matttih) said : #3

I will add details info tomorrow when I have access to the systems

actionparsnip (andrew-woodhead666) said : #4

I suggest you report a bug. I feel it will be a duplicate though. I have colleagues who have the sameissue

Matti Haack (matttih) said : #5

We found that adding the line
disable_vmware_customization: false
to /etc/cloud/cloud.cfg
fixes the issue.

What would be the right way to adress the topic and bring the line to the builds?

I can not figure out if it is a issue wiht cloud-init or open-vmware-tools, so I could not provide details for opening a bug report :(

Matti Haack (matttih) said : #6

We found that adding the line
disable_vmware_customization: false
to /etc/cloud/cloud.cfg
fixes the issue.

What would be the right way to adress the topic and bring the line to the builds?

I can not figure out if it is a issue wiht cloud-init or open-vmware-tools, so I could not provide details for opening a bug report :(

Matti Haack (matttih) said : #7

After some investigation, I was able to find the underlaying issues and the related Bug reports

it is a cloud-init issue:
https://bugs.launchpad.net/cloud-init/+bug/1788487
https://bugs.launchpad.net/cloud-init/+bug/1669875

workarounf would be:

add 'disable_vmware_customization: false' to /etc/cloud/cloud.cfg

or

as suggested by vmware:
Example: Ubuntu 18.04
1. Download Image
wget https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.vmdk
2. Convert to RAW
qemu-img convert -f vmdk -O raw bionic-server-cloudimg-amd64.vmdk bionic-server-cloudimg-amd64.raw
3. Add product_name to kernel-paramters It will be added to the environment and detected by cloud-init.
There is no way to change DMI Information on VIO/VMware instances sudo guestmount -a bionic-server-cloudimg-amd64.raw -m /dev/sda1 /mnt sudo vi /mnt/default/grub >> GRUB_CMDLINE_LINUX="product_name=\"OpenStack Nova\""
sudo guestunmount /mnt
4. Rebuild grub.cfg
sudo guestfish -a bionic-server-cloudimg-amd64.raw -m /dev/sda1 sh "grub-mkconfig -o /boot/grub/grub.cfg"
5. Convert back to vmdk
qemu-img convert -f raw -O vmdk -o adapter_type=lsilogic,subformat=streamOptimized bionic-server-cloudimg-amd64.raw ubuntu_18.04.vmdk