From: Ralf Storm <ralf.storm@konzept-is.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] HA migrate failing without error
Date: Fri, 7 May 2021 15:17:47 +0200 [thread overview]
Message-ID: <628060fd-ce79-f688-2ee0-2735542e8903@konzept-is.de> (raw)
In-Reply-To: <6c11f6a1-631b-bb22-fa34-f75e48bdc274@konzept-is.de>
I observed the error further and tried to restart some nodes, as I see
under "HA" at the Master: old timestamp - dead?
after reboot quorum is aquired as usual, but the entryfor the master
remains and no other master is elected
as i migrated some vms for the reboot - which I had to remove from HA
before, to be able to migrate them, they stuck on "deleting" in HA
as i investigated further i find this VMs to be locked under several
nodes and i can see ths strange entry on all nodes: lock--1.conf
can i force the master to change?
any other suggestions? I run out of ideas...
Am 07/05/2021 um 14:06 schrieb Ralf Storm:
> I know this behavour, but the second task does not start
>
>
> actually it seems like no host can migrate ha vms anymore, only
> without ha
>
>
>
> Am 07/05/2021 um 13:47 schrieb Aaron Lauterer:
>>
>>
>> On 5/7/21 1:34 PM, Ralf Storm wrote:
>>> Hello List,
>>>
>>> we have a cluster of 7 Nodes with ceph, all updated with subscription.
>>>
>>> since update to 6.4 we cannot ha migrate to one single node anymore,
>>> without any error, it just says " start ha migrate ok" and "End HA
>>> Migrate OK"
>>
>> That is normal. What should happen a few seconds later, is that the
>> actual migration task starts. I tested it quickly in one of my test
>> clusters and it worked.
>> First there is the 'HA <VMID> - Migrate' tags with the logs as you
>> described them. Then a few seconds later, the 'VM <VMID> - Migrate'
>> tasks starts which does the actual migration.
>>
>> Do you see that second task happening at all?
>>
>>>
>>> rebooted everything without success
>>>
>>> Migrate of NON-HA vms works like a charm to this node
>>>
>>>
>>> Anybody had a similar issue already?
>>>
>>>
>>> best regards
>>>
>>>
>>> Ralf
>>>
>>>
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user@lists.proxmox.com
>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-05-07 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 11:34 Ralf Storm
2021-05-07 11:47 ` Aaron Lauterer
2021-05-07 12:06 ` Ralf Storm
2021-05-07 13:17 ` Ralf Storm [this message]
2021-05-07 14:46 ` [LFWD] Virgil O
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=628060fd-ce79-f688-2ee0-2735542e8903@konzept-is.de \
--to=ralf.storm@konzept-is.de \
--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.