XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    Kuberenets cluster recipe not happy

    Xen Orchestra
    5
    49
    2770
    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.
    • olivierlambert
      olivierlambert Vates πŸͺ Founder & CEO 🦸 last edited by

      This or not enough RAM in the VM, explaining why fork failed to create a new thread…

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

        @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

        1 Reply Last reply Reply Quote 0
        • BenjiReis
          BenjiReis Vates πŸͺ XCP-ng Team πŸš€ last edited by

          Your VM should have 2G of RAM. Base on our Debian 10 template.
          This is really weird.

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

            @benjireis Mine says "Original Template Debian Stretch 9.0"

            1 Reply Last reply Reply Quote 0
            • BenjiReis
              BenjiReis Vates πŸͺ XCP-ng Team πŸš€ last edited by

              Weird, which templates appear in your Hub view?

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

                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

                1 Reply Last reply Reply Quote 0
                • BenjiReis
                  BenjiReis Vates πŸͺ XCP-ng Team πŸš€ last edited by

                  I do not understand how the wrong templates can be used by the recipe.

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

                    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.

                    1 Reply Last reply Reply Quote 0
                    • olivierlambert
                      olivierlambert Vates πŸͺ Founder & CEO 🦸 last edited by

                      Delete the template, maybe it's a previous version πŸ™‚

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

                        @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?

                        1 Reply Last reply Reply Quote 0
                        • olivierlambert
                          olivierlambert Vates πŸͺ Founder & CEO 🦸 last edited by

                          How do you check it's using Debian 9 template exactly?

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

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

                            P 1 Reply Last reply Reply Quote 0
                            • P
                              pnunn @mathiashedberg last edited by

                              @mathiashedberg I've just checked the ones I built that started all of this... they are deb 9.

                              Peter.

                              1 Reply Last reply Reply Quote 0
                              • olivierlambert
                                olivierlambert Vates πŸͺ Founder & CEO 🦸 last edited by

                                Can you provide a screenshot?

                                Also, double checking inside the VM that's debian 9 with a cat /etc/issue. Because the original template doesn't mean anything.

                                P 1 Reply Last reply Reply Quote 0
                                • P
                                  pnunn @olivierlambert last edited by pnunn

                                  @olivierlambert Ahh... it is 10 on the inside. 9 on the wrapper πŸ™‚

                                  1 Reply Last reply Reply Quote 0
                                  • olivierlambert
                                    olivierlambert Vates πŸͺ Founder & CEO 🦸 last edited by

                                    You can create a Debian 10 VM using a Debian 9 template, it doesn't matter (both are HVM guests, same config).

                                    The current VM was probably made while Debian 10 template wasn't there yet.

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

                                      @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.

                                      M 1 Reply Last reply Reply Quote 0
                                      • olivierlambert
                                        olivierlambert Vates πŸͺ Founder & CEO 🦸 last edited by

                                        Are you sure you removed the templates?

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

                                          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)

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

                                            @olivierlambert Ill remove them using the windows client

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