Kuberenets cluster recipe not happy
It's a bit off topic but:
- Remember, snapshot is not backup
- You can use XO from the sources to have all XO source code without feature restrictions (but XO hub/recipe is XOA because it's a service connected on xen-orchestra.com where we host the machines).
Anyway, let's try to find the original problem
@mathiashedberg said in Kuberenets cluster recipe not happy:
@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.
Xen Orchestra is free and open source. You can follow the build from source instructions or use a script like the one posted to my github
mathiashedberg last edited by
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.
@mathiashedberg the snaphots might be indeed the problem.
When looking for the template, the recipe looks for a VM with
xo:resource:xva:id=<template uuid>in its
other-config, a snapshot of the template VM would probably have this field se and it should not.
Can you check if it's the case? and if the
That's an interesting thing. I think it might be a potential bug because of XenCenter snapshot algorithm that handle
is-templatedifferently than XO.
@olivierlambert should I also check that
Double check what do you have when we install a template from XO Hub. If
is-a-snapshotis at false, then yes, add this condition. We should use the installed template, not anything else.
Okay so a fix is coming soon, i'll update here once released.
mathiashedberg last edited by mathiashedberg
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
@mathiashedberg good to know.
So you can wait for the fix or remove the
other_configsof the snapshots or remove the snapshots
mathiashedberg last edited by
@benjireis Looks like version 5.56.0 runs as expected! No issues so far!
Thanks for the feedback @mathiashedberg !