Not sure if it should be posted here or in PVE, but I do it here since the migration will be startet using the PDM GUI.
Simplified setup:
Datacenter "Site A"
node1.sitea.company.com
node2.sitea.company.com
node3.sitea.company.com
Datacenter "Site B"
node4.siteb.company.com
node5.siteb.company.com
node6.siteb.company.com
All nodes are added to PDM and show up nicely in the dashboard with fqdn and are fully resolvable.
Trying a cross site migration from node 1 to node 4 gives error "pdm api error (status = 400: api error (status = 500: 500 Can't connect to node4:8006 (Temporary failure in name resolution) ))"
Further examination shows: PVE node1 tries to lookup "node4" as plain host, not using its fqdn.
Since node1 is in Site A it has a search list of only "sitea.company.com", so it's not able to resolve node4 (this resides under node4.siteb.company.com).
Solution 1: add siteb.company.com to node1's search list in /etc/resolv.conf (and vice versa).
Solution 2: add a CNAME for node4 under sitea.company.com: "node4 IN CNAME node4.siteb.company.com.".
I think different DNS zones for different sites are very common, so PDM should be able to handle this using fqdn.
I'm using PDM 1.0.2 (current) with PVE 9.1.5.
Simplified setup:
Datacenter "Site A"
node1.sitea.company.com
node2.sitea.company.com
node3.sitea.company.com
Datacenter "Site B"
node4.siteb.company.com
node5.siteb.company.com
node6.siteb.company.com
All nodes are added to PDM and show up nicely in the dashboard with fqdn and are fully resolvable.
Trying a cross site migration from node 1 to node 4 gives error "pdm api error (status = 400: api error (status = 500: 500 Can't connect to node4:8006 (Temporary failure in name resolution) ))"
Further examination shows: PVE node1 tries to lookup "node4" as plain host, not using its fqdn.
Since node1 is in Site A it has a search list of only "sitea.company.com", so it's not able to resolve node4 (this resides under node4.siteb.company.com).
Solution 1: add siteb.company.com to node1's search list in /etc/resolv.conf (and vice versa).
Solution 2: add a CNAME for node4 under sitea.company.com: "node4 IN CNAME node4.siteb.company.com.".
I think different DNS zones for different sites are very common, so PDM should be able to handle this using fqdn.
I'm using PDM 1.0.2 (current) with PVE 9.1.5.