BurmillaOS in Proxmox VE environment with CloudDrive (cloud-init)

[prologic]

Hey folks 👋

I"m actually having a lot of trouble trying to get Burmilla OS working properly in Proxmox VE with cloud-init in an automated way. I actually run Burmilla OS (several) nodes in Proxmox VE just fine, but those VM(s) were created with other tools.

The problem I'm seeing is describe as follows:

• The VM has a CloudDrive attached with some cloud-init values that Proxmox VE supports
• I can see that CloudDrive on /dev/sr1 if I login to the Burmilla OS VM in autologin mode and I can mount it.
• I can also see the user-data in that media.

But...

Burmilla OS doesn't seem to do anything with it. Despite it claiming the datasources is listed as /media/config-2 (I'm not sure what this path is meant to be?). The docs' boot process actually claims:

Userdata is a file given by users when launching BurmillaOS hosts. It is stored in different locations depending on its format. If the userdata is a cloud-config file, indicated by beginning with #cloud-config and being in YAML format, it is stored in /var/lib/burmilla/conf/cloud-config.d/boot.yml. If the userdata is a script, indicated by beginning with #!, it is stored in /var/lib/burmilla/conf/cloud-config-script.

But this is not the case I do not see a boot.yml there or any evidence it tried to load the CloudDrive cloud-init config.

Any hints as to what's going on?

[prologic]

I have a little extra info from inspecting the /var/log/boot/init.log looking for signs of why it hasn't loaded
and executed the user-data on the CloudDrive on /dev/sr1; found this:

Sorry this isn't text, I obviously can't SSH into the VM 😂

[prologic]

Configdrive was enabled but has no configdrive device or filesystem, ignore cloudinit

[prologic]

This old Rancher OS issue might be related, I'm reading it now...

[prologic]

Looks like we're hitting this section of code:

os/pkg/init/cloudinit/cloudinit.go

Lines 51 to 61 in 0dc7a00

	if onlyConfigDrive(cfg.Rancher.CloudInit.Datasources) {
	configDev := util.ResolveDevice("LABEL=config-2")
	if configDev == "" {
	// Check v9fs: https://www.kernel.org/doc/Documentation/filesystems/9p.txt
	matches, _ := filepath.Glob("/sys/bus/virtio/drivers/9pnet_virtio/virtio*/mount_tag")
	if len(matches) == 0 {
	log.Info("Configdrive was enabled but has no configdrive device or filesystem, ignore cloudinit")
	return cfg, nil
	}
	}
	}

[prologic]

Am I reading this code correctly?! 😳 We hard-code the label of the block-device we look for and only look for one, named config-2? Who came up with this name? And who decides it would be cidadta in other places? 😱

[prologic]

I think this is the NoCloud data source hmmm 🤔 -- Maybe I can reconfigure the default datasource used in my Packer image's configuration when I install Burmilla OS to disk?

[olljanat]

Didn't read all those comments (yet) but first of all. Are you new with BurmillaOS without earlier RancherOS experience? And if so I'm very interested to here why you decided to use BurmillaOS instead of something else?

And if not, then are those same bugs already on RancherOS?

[prologic]

Didn't read all those comments (yet) but first of all. Are you new with BurmillaOS without earlier RancherOS experience? And if so I'm very interested to here why you decided to use BurmillaOS instead of something else?

And if not, then are those same bugs already on RancherOS?

No I'm not new to Rancher OS at all 😁 Have been using it in Proxmox VE 5+ years 🤣

I switched to Burmilla OS for the same reasons anyone else did. Rancher Labs no longer maintains the wonderful Rancher OS 😥

[prologic]

Related discussion Telmate/terraform-provider-proxmox#405

[prologic]

Appreciate any help here 🤗 I've dug quite a bit into three codebases (Packer Proxmox plugin, Burmilla OS and the Proxmox Terraform Provider) I'm not sure how to solve this... (yet? :D)

[olljanat]

I haven't use Terraform for a while and never with ProxmoxVE but can you define the path where cloud-init is stored on ISO file? We use cloud-init OpenStack provider and that at least works just fine. Example from one of our servers:

$ mount /dev/sr0 /mnt/
$ head -n 3 /mnt/openstack/latest/user_data
#!/bin/bash
echo "$(date +"%F %T") Cloud-config started" | tee -a $0.log

[olljanat]

Maybe @PrplHaz4 or @jokay help here? I don't have ProxmoxVE lab at the moment.

[jokay]

Yes, we use ProxmoxVE but without cloud-init / cloud drive.

We setup our hosts according to the documentation, see here.