Created cloud config, but can't select it when creating a new VM.

olivierlambert

What OS are you using?

eperez539

@olivierlambert I tried it with Ubuntu 18.04 and installed cloud init when creating the template.

olivierlambert

So you need to check cloudinit logs in your VM to understand why it doesn't fetch your config.

eperez539

@olivierlambert Seems like the cloud init config that gets run is the one under:

/var/lib/cloud/seed/nocloud-net/user-data

Have checked all the different logs and there is nothing about the custom cloud-init config that I selected during VM creation using XenOrchestra.

geek-baba

@olivierlambert - I was trying Debian cloud template for XenServer with Debian 10, the installation process mostly works except 'dpkg-reconfigure cloud-init' does not bring up data source selection window. I also read XO Cloudinit guide which talks about openstack vs nocloud config drive, however I have tried the defaults and cloud config tab, but the VM does not pick up the cloud init settings, not sure if I should start a new topic or not but having similar issue.

olivierlambert

Please try with our Debian template in XO Hub.

geek-baba

@olivierlambert I wish, the community edition does not have hub support I believe.

olivierlambert

You can try with XOA Free

geek-baba

@olivierlambert I will certainly try that, however I wanted to customize it for k8s cluster, so was wondering if the old guide need updating if at all.

olivierlambert

If we can find exactly why, yes we could improve/fix it

geek-baba

@olivierlambert - ok, I will continue troubleshooting, the guide is pretty basic, i.e. install plain vanilla debian and install couldinit so was not sure what could go wrong.

olivierlambert

Partition ID for Cloudinit is the first step to check.

apt-get install cloud-init cloud-initramfs-growroot

diff /usr/lib/cloud-init/ds-identify.ORIGINAL /usr/lib/cloud-init/ds-identify
236a237,238
>             LABEL_FATBOOT=*) label="${line#LABEL_FATBOOT=}";
>                               labels="${labels}${line#LABEL_FATBOOT=}${delim}";;

/etc/cloud/cloud.cfg

ssh_deletekeys: true

datasource_list: [ ConfigDrive, None ]
datasource:
  ConfigDrive:
    dsmode: local

eperez539

@olivierlambert just tried to go through the process again from what the example gave. Included the extra lines you mentioned above for the datasource. But it is still not seeing any of the custom cloud init settings that I configured.

Is the template VM somehow badly configured? Is there anything on here that is outdated: https://xen-orchestra.com/blog/centos-cloud-template-for-xenserver/

I'll continue debugging this issue but would be nice to have a guide on how to make cloud init work. Seems like there is something either missing or not working on the current guide (maybe XO bug?).

Looking at the docs again, seems like the cloud-init config didn't really work:

Hostname is set to: cloudtest

Result (host name is not correct )

geek-baba

@eperez539 this guide wont work, this is what I did, installed XOA, created the VM from HUB, modified it and converted again to the template.

eperez539

@geek-baba Thanks, do you happen to have some steps on the additional changes you made to the VM before converting in to the template?

geek-baba

@eperez539 just install anything you want, for example I added docker and kubernetes and converted it to template and now when I create new VM it retains everything.

eperez539

@geek-baba oh ok, so are you bypassing cloud init altogether? How do you handle the network config? I was hoping to at least setup network + ssh key and then I could mange with Ansible after that.

Initially tried using Terraform with XO, but this cloud init issue may be the problem why I was having an issue getting them to work together.

geek-baba

no I am not bypassing the cloudinit, I am using a working template that have local cloud config that I was not able to get it working on my own. if you use the template, you would see 2 drives under disk like below.

alt text

MrMike

@olivierlambert said in Created cloud config, but can't select it when creating a new VM.:

your VM to understand why it doesn't fetch your config.

There was a an update to cloud-init recently and it broke the template I've been using to deploy our VMs. What's i've noticed so far is that it overwrites the network configuration files for centos in /etc/sysconfig/network-scripts/ifcfg-eth0. I got around that issue by adding the network: configuration: ignore to the cloud.cfg file..

I then figured maybe it's time to update my template, so I went ahead and did just that using the same guide found here.

Once the VM starts it also fails to load the config drive automatically, so I'm thinking the documentation will need to get some sort of refresh .. Once I figure it out, I can show what worked for me here if no one else figured it out first.

olivierlambert

Keep us posted please