Unknown error - this pool is already connected
-
I'm far too busy to read in details, but @Danp's answer seems right to me
-
@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.
-
@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.
-
@rkelley Have you tried restarting
xo-serveror rebooting the XO VM? -
@danp Yes, just rebooted XOA. Problem still exists.
-
@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"? -
What? You shouldn't have any slave in Settings/server, just the IP of the pool master, that's it.
-
@olivierlambert
So, they are safe to delete? -
@abrehmc More than safe to delete, you need to delete them.
-
Yes, you are not meant to add slaves in there.
-
@olivierlambert
Thanks guys
