From: Lindsay Mathieson <lindsay.mathieson@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Can't migrate my HA VM's
Date: Sun, 26 Jul 2020 11:14:10 +1000 [thread overview]
Message-ID: <134f41a7-1c51-53ea-7144-78a73e7a709b@gmail.com> (raw)
In-Reply-To: <88d992dc-5d46-f639-bd63-a721d0a51ab2@gmail.com>
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
prev parent reply other threads:[~2020-07-26 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 1:08 Lindsay Mathieson
2020-07-26 1:14 ` Lindsay Mathieson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=134f41a7-1c51-53ea-7144-78a73e7a709b@gmail.com \
--to=lindsay.mathieson@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.