Re: [pve-devel] [PATCH container 1/2] Fix #1547: on migration abort, the CT starts again

looks good, only one small sytax error: > + # in restart mode, we start the container on the source node > + # on migration error > + if ($self->{opts}->{restart} && $self->{was_running}) { > + $self->log('info', "start container on source node"); > + my skiplock = 1;

[pve-devel] [PATCH container 1/2] Fix #1547: on migration abort, the CT starts again

When a migration fails, the final_cleanup phase now starts the container on the source node again, if it was a migration in restart_mode and the CT was running. Signed-off-by: Alwin Antreich --- src/PVE/API2/LXC/Status.pm | 8 +--- src/PVE/LXC.pm | 14