On 02/24/2016 10:34 AM, Dietmar Maurer wrote: >> If we get an 'EWRONG_NODE' error from the migration we have no sane >> way out. If we place it then in the started state we also get the >> 'EWRONG_NODE' error again and it even will place the service in >> the migration state again (when it's not restricted by a group) and >> thus result in an infinite started <=> migrate cycle. > Is there a regression test case for this situation?
I'll try to create one and send it as reply here. The situation with the applied sync patches is now way less error prone to this problem, normally we even shouldn't get into this case anymore if nobody tampers with the VMs by hand. _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
