XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Kuberenets cluster recipe not happy

    Scheduled Pinned Locked Moved Xen Orchestra
    49 Posts 5 Posters 15.0k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • BenjiReisB Offline
      BenjiReis Vates 🪐 XCP-ng Team @mathiashedberg
      last edited by

      @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 is-template field is true.

      M 1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        That's an interesting thing. I think it might be a potential bug because of XenCenter snapshot algorithm that handle is-template differently than XO.

        BenjiReisB 1 Reply Last reply Reply Quote 0
        • BenjiReisB Offline
          BenjiReis Vates 🪐 XCP-ng Team @olivierlambert
          last edited by

          @olivierlambert should I also check that is-a-snapshot is false?

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Double check what do you have when we install a template from XO Hub. If is-a-snapshot is at false, then yes, add this condition. We should use the installed template, not anything else.

            1 Reply Last reply Reply Quote 0
            • BenjiReisB Offline
              BenjiReis Vates 🪐 XCP-ng Team
              last edited by

              Okay so a fix is coming soon, i'll update here once released. 🙂

              1 Reply Last reply Reply Quote 0
              • M Offline
                mathiashedberg @BenjiReis
                last edited by mathiashedberg

                @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
                
                BenjiReisB 1 Reply Last reply Reply Quote 0
                • BenjiReisB Offline
                  BenjiReis Vates 🪐 XCP-ng Team @mathiashedberg
                  last edited by

                  @mathiashedberg good to know.

                  So you can wait for the fix or remove the xo:resource:xva:id from the other_configs of the snapshots or remove the snapshots

                  M 1 Reply Last reply Reply Quote 0
                  • M Offline
                    mathiashedberg @BenjiReis
                    last edited by

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

                    1 Reply Last reply Reply Quote 2
                    • olivierlambertO Offline
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by

                      Thanks for the feedback @mathiashedberg !

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post