ustom RAS Provider (HPE VM Essentials) — clone fails after template versioning, appears to be a Morpheus backup/clone naming mismatch

We're using a Custom Provider Framework script to integrate Parallels RAS with HPE VM Essentials for template-based provisioning. Basic provisioning (deploying new machines from a template) works fine. However, the "create a new template version, then deploy from it" workflow consistently fails at the deploy/clone step.

What works
  • Provider/connect, guests/list, guests/get, guests/control (start/stop/etc.)
  • Converting an instance to a RAS template
  • Creating a new snapshot/version on the template (PUT /api/instances/{id}/snapshot) — this succeeds and is visible both via the Morpheus/VME UI (Snapshots tab, e.g. RAS_TEMPLATE_VERSION_3) and on the underlying KVM host.

What fails

Deploying an instance from the newly versioned template fails in RAS with:
Failed to create server volumes: Failed to clone volume: cp: cannot stat<br>'/mnt/datastore/&lt;instance-name&gt;/hvm_&lt;id&gt;-disk-0-&lt;uuid&gt;-copy-for-backup': No such file or directory


Has anyone successfully implemented "create new template version → deploy from a specific version" against HPE VM Essentials via the RAS Custom Provider Framework, and if so, what does your snapshot/backup/clone sequence look like?
 
Back
Top