Ok, I resolved the issue, though maybe it exposes a problem?
I had a test Proxmox Backup server Beta, which I took down and erased,
but I left the storage entry. Once I deleted the Storage entry, the HA
VM's were able to migrate.
Would seem to be an issue if HA VM's can't be migrated if a backup
server is down.
On 26/07/2020 11:08 am, Lindsay Mathieson wrote:
Have this error start today when I attempt to migrate my HA managed VM's
task started by HA resource agent
2020-07-26 10:55:00 starting migration of VM 101 to node 'vnb'
(192.168.5.240)
2020-07-26 10:55:02 ERROR: Failed to sync data - proxmox-backup-client
failed: Error: error trying to connect: tcp connect error: No route to
host (os error 113)
2020-07-26 10:55:02 aborting phase 1 - cleanup resources
2020-07-26 10:55:02 ERROR: migration aborted (duration 00:00:02):
Failed to sync data - proxmox-backup-client failed: Error: error
trying to connect: tcp connect error: No route to host (os error 113)
TASK ERROR: migration aborted
All servers are pingable from each other (static entries in host
files). If I remove the VM from HA it migrates fine. Dunno when this
started, but I used to be able to migrate HA managed VM's.
All updates applied, non-subscription repository.
Haven't tested restarting any services yet.
--
Lindsay
--
Lindsay
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
