Fohdeesha
commented
5 years ago When you say coreOS template, do you mean you've already set up a coreOS VM with the xenserver docker plugin installed, then converted it to a template? Or are you booking the cloud-init ISO directly?
We recently changed how config data is presented in cloudinit from openstack to nocloud drive type, this allows us to also pass networking config info to VMs. Default cloudinit installs are set to look for both these drive types. It sounds like your install of cloud-init is set to only look for the openstack drive type. There is some info on how to check this in our docs: https://xen-orchestra.com/docs/cloudinit.html#requirements
If you're booting directly from the ISO, it's possible CoreOS has set their instance of cloud-init to only look for openstack config drive types, which would not make much sense, but it's possible. As for the containers tab, this is not handled by the cloudinit instance as far as I know so I am not sure if the missing tab is related to this change.
GiorgioAresu
Hi, I'm testing XOA before using it with XCP-ng to replace ESXi, but I'm having issues with coreos template. I'm positive it's a XOA issue because it happens only after I register for the trial and let it update
Expected behavior
I create a VM based on CoreOS template, fill the form appropriately and submit. If I use the default (outdated) cloud-config, the VM boots, and CoreOS shows an error about it. If I use an updated one (this) and add my ssh key, the VM boots, and I'm able to log in via SSH. Either way I can see the container tab.
Current behavior
After the registration and update, I do the same. The VM boots, CoreOS shows no errors both with the outdated config as with the updated one, but I'm not able to log in via SSH. It seems to completely ignores the config and takes a default one. I can NOT see the container tab