Error adding host to existing pool

guillemrebull

Continuing with the migration of vmware to XCP-ng I am facing the following problem.

I have removed vmware from my second host and I have it ready to add to the existing pool.

I got the following error: POOL_JOINING_HOST_HAS_NON_MANAGEMENT_VLANS()

I checked that both host 1 and host 2 had management.

The peculiarities are that both hosts are on vlan90
the master has 192.168.90.55 and the slave 192.168.90.57

I also thought that the problem was that they did not have the same vlans.
I put both hosts with the same vlans but the problem continues.

Can you help me?

Log error: pool.mergeInto
{
  "sources": [
    "7798f8c1-7cea-3d3f-8c43-75fe48b056cc"
  ],
  "target": "9f1b93a6-eea2-3cd4-da77-ecf5afa1a66d",
  "force": true
}
{
  "code": "POOL_JOINING_HOST_HAS_NON_MANAGEMENT_VLANS",
  "params": [],
  "call": {
    "method": "pool.join_force",
    "params": [
      "192.168.90.55",
      "root",
      "* obfuscated *"
    ]
  },
  "message": "POOL_JOINING_HOST_HAS_NON_MANAGEMENT_VLANS()",
  "name": "XapiError",
  "stack": "XapiError: POOL_JOINING_HOST_HAS_NON_MANAGEMENT_VLANS()
    at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202312051521/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202312051521/packages/xen-api/transports/json-rpc.mjs:35:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
    at process.callbackTrampoline (node:internal/async_hooks:128:17)"

olivierlambert

You need to have a host that doesn't have any network configured already (outside management), because the config will be wiped and replaced by the destination pool config.

guillemrebull

@olivierlambert Thank you for your prompt response.

If I understood correctly, the slave host only needs to have the manager network configured.

But I have more vlans that access the shared sr. Do I have to configure these later?

olivierlambert

As soon your host enters the pool, the network configuration (and storage) will be propagated to the new pool member.

guillemrebull

@olivierlambert I'll try it!

guillemrebull

@olivierlambert Now it has been added,

But it has also copied the vlan configurations with the network cards....

Is that so?

If on host 1 in eth1 I had vlan 40 for storage
on host 2 do I have to have it the same?

Can't I have it on eth4???

olivierlambert

No, you have to use the same NIC numbering between the hosts in the pool, that's part of the perk using a pool, the configuration is auto applied on all your hosts.

If you have a different number of NICs you must use interface rename program to try to get them ordered the same at least. If the hardware is too different, then using a pool isn't what you need.

guillemrebull

@olivierlambert Ok, understood.

The issue is that the current server which is master is the most different from the other 4 we have.

We have this fifth one for testing and migrations.

The others are all the same.

Can VMs be migrated in different pools?

Could one host be changed from master to another once we have the same ones in the same pool??

Thanks in advance.

olivierlambert

So you can do the opposite if you prefer, create a pool with the other hosts instead. Yes, you can live migrate between pools. Or warm migrate. Anyway, everything is possible, it's just a matter of understanding the pro and cons of using pools.

guillemrebull

@olivierlambert Thank you very much for the info.

Better this way, I will create a pool with the 4 equal hosts.

olivierlambert

Yeah I think that's the best approach in your case