[pve-devel] [PATCH v2 container 12/18] skip pending changes while cloning

Thomas Lamprecht t.lamprecht at proxmox.com
Wed Oct 2 12:33:52 CEST 2019


some rationale here would be great, e.g.:

> we only can clone from the current applied state, as else
> the on-disk state may not match the one from the config. Further
> this makes it more consistent with the qemu-server behavior.

On 9/30/19 2:44 PM, Oguz Bektas wrote:
> Signed-off-by: Oguz Bektas <o.bektas at proxmox.com>
> ---
>  src/PVE/API2/LXC.pm | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
> index 9c040d1..2cb9f9d 100644
> --- a/src/PVE/API2/LXC.pm
> +++ b/src/PVE/API2/LXC.pm
> @@ -1441,6 +1441,7 @@ __PACKAGE__->register_method({
>  		# Replace the 'disk' lock with a 'create' lock.
>  		$newconf->{lock} = 'create';
>  
> +		delete $newconf->{pending};
>  		delete $newconf->{template};
>  		if ($param->{hostname}) {
>  		    $newconf->{hostname} = $param->{hostname};
> 





More information about the pve-devel mailing list