VMInstance.memory is stored in MB and disk_size in GB (see _bytes_to_mb/
_bytes_to_gb in monitoring_worker.py), but the reinstall worker divided
them again by 1024*1024 / 1024**3 as if they were raw bytes. Both
computations collapsed to 0, so the post-clone "re-apply config" and
"restore disk size" steps silently no-op'd - reinstalled VMs/containers
ended up with the template's own memory and disk size instead of the
instance's previous values.