[pve-devel] [PATCH] migrate : add nocheck for resume

Thomas Lamprecht t.lamprecht at proxmox.com
Thu Oct 15 09:26:33 CEST 2015


Yes, exactly.Actually we test if the config file moved, if not the migration is marked as failed else it is marked as succeed.But we should place the API call in an eval statement, else the config check won't get executed when the call has an error.

----- Reply message -----
Da: "Dietmar Maurer" <dietmar at proxmox.com>
A: "Alexandre DERUMIER" <aderumier at odiso.com>, "PVE development discussion" <pve-devel at pve.proxmox.com>
Oggetto: [pve-devel] [PATCH] migrate : add nocheck for resume
Data: gio, ott 15, 2015 07:23

> >>I'll try to make the HA "immune" against such errors, but the real bug 
> >>isn't in the HA stack :)
> 
> Yes, I think we could send different error code for errors in phase3 of live
> migration.
> Maybe a warning instead an error for this phase.

I think the LRM can easily test if the VM Config file was moved or not, so we
can do the check inside the LRM.

_______________________________________________
pve-devel mailing list
pve-devel at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pve.proxmox.com/pipermail/pve-devel/attachments/20151015/45472571/attachment-0001.html>


More information about the pve-devel mailing list