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

    Unknown error - this pool is already connected

    Scheduled Pinned Locked Moved Xen Orchestra
    14 Posts 5 Posters 2.7k 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.
    • R Offline
      rkelley @Danp
      last edited by

      @danp I am getting this message when adding more standalone servers to XO. These servers used to be in a cluster before the cluster was messed up.

      Thanks for the pointers on cleaning up XO. Before I do that, I want @olivierlambert to have a chance to review the log files in case I have run into a bug with XO.

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

        I'm far too busy to read in details, but @Danp's answer seems right to me 🙂

        1 Reply Last reply Reply Quote 0
        • DarkbeldinD Offline
          Darkbeldin Vates 🪐 Pro Support Team @rkelley
          last edited by

          @rkelley Could you be more clear on what you are trying to do, because you should'nt try to add your slave to XO they will be pulled in when you add the master.

          If you try to add hosts that was on the pool before but that are standalone now did you reinstalled it because they probably have the infos from the old pool and that's why you can't add them to XO.

          R 1 Reply Last reply Reply Quote 0
          • R Offline
            rkelley @Darkbeldin
            last edited by

            @darkbeldin Here are the steps I used:

            • Install 3 node cluster with XCP-NG 8.2
            • Install XOA
            • Reconfigure mgmt interface - lose all access to XCP-NG cluster.
            • Try to force-remove (eject) nodes from cluster. Unsuccessful.
            • Remove nodes from XOA
            • Reinstall XCP-NG on nodes - without HA (nodes are standalone)
            • Add node-1 to XOA; good
            • Add node-2 to XOA - Error: This pool is already connected
            • Add node-3 to XOA - Error: This pool is already connected

            It seems XOA is not cleaning up some internal data structures if it sees the new standalone nodes as part of an old cluster. This seems like a bug to me.

            DanpD 1 Reply Last reply Reply Quote 0
            • DanpD Offline
              Danp Pro Support Team @rkelley
              last edited by

              @rkelley Have you tried restarting xo-server or rebooting the XO VM?

              R 1 Reply Last reply Reply Quote 0
              • R Offline
                rkelley @Danp
                last edited by

                @danp Yes, just rebooted XOA. Problem still exists.

                A 1 Reply Last reply Reply Quote 0
                • A Offline
                  abrehmc @rkelley
                  last edited by

                  @rkelley said in Unknown error - this pool is already connected:

                  @danp Yes, just rebooted XOA. Problem still exists.

                  We have the exact same problem, all slave servers have that error also after reboot.
                  Is slave servers supposed to be here in the first place? The XOA has all hosts listed "Home/Hosts) and by "pool" I guess it means "Master".
                  I had one missing slave server, but adding it just gave the error.
                  Can we delete all servers that does not have a pool listed by them under "Settings/Servers"?

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

                    What? You shouldn't have any slave in Settings/server, just the IP of the pool master, that's it.

                    A 1 Reply Last reply Reply Quote 0
                    • A Offline
                      abrehmc @olivierlambert
                      last edited by

                      @olivierlambert
                      So, they are safe to delete?

                      DarkbeldinD 1 Reply Last reply Reply Quote 0
                      • DarkbeldinD Offline
                        Darkbeldin Vates 🪐 Pro Support Team @abrehmc
                        last edited by

                        @abrehmc More than safe to delete, you need to delete them.

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

                          Yes, you are not meant to add slaves in there.

                          A 1 Reply Last reply Reply Quote 0
                          • A Offline
                            abrehmc @olivierlambert
                            last edited by

                            @olivierlambert
                            Thanks guys

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