> 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? _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
