@olivierlambert HA is disabled on the pool level

@olivierlambert Hmm im not sure how i can check that. It was configured via XOA, however the VMs were live migrated from a different host which has been decomissioned. Maybe there is some pool HA going on?

Im having issues with the auto start feature.

If i experience a power loss on my server, the VMs dont start. Is this expected behaviour?
My server stays on 24/7, so i dont have not been able to check that autostart functions on reboot, however i can check that too if needed.
Running xe vm-param-list uuid=<uuid> | grep other-config gives me the expected auto_poweron: true;. Is there anything else to check?

@benjireis Looks like version 5.56.0 runs as expected! No issues so far!

@benjireis
So you are correct on all those points. Here are the relevant params from the snapshot that was being used:

is-a-template ( RW): true
is-a-snapshot ( RO): true
other-config (MRW): auto_poweron: false; xo:resource:xva:id: a677aa91-f5d5-46ec-bd53-956b73fc7871; xo:resource:namespace: Debian10; xo:resource:xva:version: 1.0.0; import_task: OpaqueRef:71bd99c2-11c3-4306-a5b9-7fe6e86f551b; mac_seed: 02166646-6e3b-de07-1b11-872d538d3f01; base_template_name: Debian Stretch 9.0; install-methods: cdrom,nfs,http,ftp; linux_template: true

@olivierlambert
The snapshot functionality is still quite tempting to use, as I have not had any issues with it before now. I'll admit I'm not too up to date on what features are recommended or not when it comes to XCP-NG.

@DustinB I think its great that we have such useful software that is free and open source. If my comment came off as negative I apologize, that was not my intention.

Moving forward I would assume that removing all my snapshots would remedy the issue. However I'm not too sure on how keen I am on doing that right at this moment with my current setup, maybe on a different test lab.

@olivierlambert For a homelab setup this is currently the only "free" solution to snapshotting that i know of (other than file system based like ZFS).

Going from "free" to 77USD a month is quite a jump imo.

@olivierlambert Yes i removed it from the Hub > Templates view. It should be noted that i take regular backups of the VMs created with this debian 10 template, so i think it is using them

Backups are done with the XCP-NG center: 'Pool' > 'VM Snapshot Schedule' setting

@olivierlambert Ill remove them using the windows client

So this new VM for k8s seems to be based on an existing VM, which itself is based on the Debian 10 template (when it was created a long time ago)

@olivierlambert

So after some more testing it seems the template mapping is wrong again. My k8s VMs started with 500MB, and when i looked at the bash history, i saw that yet again, the k8s VMs were based on an existing VM running on the system. The ram was set to 500MB because thats what the base VM ram settings were. This is the same issue as earlier on.

@olivierlambert Under the VM page "Advanced" > "Misc"

@olivierlambert I deleted all templates from XOA by going to "Hub" > "Templates" and using the trash icon to remove them. However it still appears that it uses debian 9. I could try to remove all templates from the system via the windows xcp-ng client. However it may be of importance to know that i have never used the debian 9 template before. While using this recipe was the first time i saw it.

I remember trying the k8s recipe about a year ago, maybe that has tainted my setup in some way?

Yes it is quite strange.

This XOA has been in use for some time with a couple of pools added and removed over time, so I may be an edge case here.

Just the standard ones:

• Alpine 3.10
• Centos 8.0
• Debian 10
• pfsense 2.4

My XOA has two pools

This issue is similar to the one i had earlier, where the image was being based on a different existing VM, now in this case its the debian 9 template.
I know the debian 10 template works fine as this is what i normally use

@benjireis Mine says "Original Template Debian Stretch 9.0"

@olivierlambert @BenjiReis
Im also guessing too little RAM. The VMs were started with only 500MB, which i found strange. Any way for me to change this on initialization?

Im guessing i could change the Debian 9 template

@benjireis
Looks like that fixed that issue. Now there is an issue with the cloud-config. Seems like gnupg2 is not installed

sudo systemctl status cloud-final.service
● cloud-final.service - Execute cloud user/final scripts
   Loaded: loaded (/lib/systemd/system/cloud-final.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2021-02-15 09:20:37 EST; 5min ago
  Process: 649 ExecStart=/usr/bin/cloud-init modules --mode=final (code=exited, status=1/FAILURE)
 Main PID: 649 (code=exited, status=1/FAILURE)

Relevant snippet: I could send you the whole snippet from sudo journalctl -u cloud-final.service if you would like

Feb 15 09:20:34 node-1 cloud-init[649]: 0 added, 0 removed; done.
Feb 15 09:20:34 node-1 cloud-init[649]: Running hooks in /etc/ca-certificates/update.d...
Feb 15 09:20:34 node-1 cloud-init[649]: done.
Feb 15 09:20:34 node-1 cloud-init[649]: Errors were encountered while processing:
Feb 15 09:20:34 node-1 cloud-init[649]:  linux-image-4.19.0-14-amd64
Feb 15 09:20:34 node-1 cloud-init[649]:  linux-image-amd64
Feb 15 09:20:34 node-1 cloud-init[649]: FATAL -> Failed to fork.
Feb 15 09:20:34 node-1 cloud-init[649]: Cloud-init v. 18.3 running 'modules:final' at Mon, 15 Feb 2021 14:19:26 +0000. Up 15.00 seconds.
Feb 15 09:20:34 node-1 cloud-init[649]: 2021-02-15 14:20:34,984 - util.py[WARNING]: Package upgrade failed
Feb 15 09:20:35 node-1 cloud-init[649]: Reading package lists...FATAL -> Failed to fork.
Feb 15 09:20:35 node-1 cloud-init[649]: 2021-02-15 14:20:35,124 - util.py[WARNING]: Failed to install packages: ['apt-transport-https', 'ca-certificates', 'curl', 'gnupg2', 'software-properties-common']
Feb 15 09:20:35 node-1 cloud-init[649]: 2021-02-15 14:20:35,127 - cc_package_update_upgrade_install.py[WARNING]: 2 failed with exceptions, re-raising the last one
Feb 15 09:20:35 node-1 cloud-init[649]: 2021-02-15 14:20:35,128 - util.py[WARNING]: Running module package-update-upgrade-install (<module 'cloudinit.config.cc_package_update_upgrade_install' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_package_update_upgrade_in
Feb 15 09:20:35 node-1 cloud-init[649]: /var/lib/cloud/instance/scripts/runcmd: 2: /var/lib/cloud/instance/scripts/runcmd: curl: not found
Feb 15 09:20:35 node-1 sudo[17486]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/apt-key add -
Feb 15 09:20:35 node-1 sudo[17486]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 15 09:20:35 node-1 cloud-init[649]: E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
Feb 15 09:20:35 node-1 cloud-init[649]: /var/lib/cloud/instance/scripts/runcmd: 3: /var/lib/cloud/instance/scripts/runcmd: curl: not found
Feb 15 09:20:35 node-1 sudo[17486]: pam_unix(sudo:session): session closed for user root
Feb 15 09:20:35 node-1 sudo[17505]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/apt-key add -
Feb 15 09:20:35 node-1 sudo[17505]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 15 09:20:35 node-1 cloud-init[649]: E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
Feb 15 09:20:35 node-1 cloud-init[649]: /var/lib/cloud/instance/scripts/runcmd: 4: /var/lib/cloud/instance/scripts/runcmd: add-apt-repository: not found
Feb 15 09:20:35 node-1 cloud-init[649]: /var/lib/cloud/instance/scripts/runcmd: 5: /var/lib/cloud/instance/scripts/runcmd: add-apt-repository: not found
Feb 15 09:20:35 node-1 sudo[17505]: pam_unix(sudo:session): session closed for user root
Feb 15 09:20:35 node-1 cloud-init[649]: Hit:1 http://security.debian.org buster/updates InRelease
Feb 15 09:20:35 node-1 cloud-init[649]: Hit:2 http://deb.debian.org/debian buster InRelease
Feb 15 09:20:35 node-1 cloud-init[649]: Hit:3 http://deb.debian.org/debian buster-updates InRelease
Feb 15 09:20:35 node-1 cloud-init[649]: Hit:4 http://deb.debian.org/debian buster-backports InRelease
Feb 15 09:20:36 node-1 cloud-init[649]: Reading package lists...

@benjireis
Yes currently the issue is with version 5.54.0. Tested about an hour ago