Issue/Introduction

This article helps troubleshoot cases where ZSphere cloning cannot find backup storage or commit a volume snapshot as an image.

Symptoms

• Creating a cloning task fails with an error indicating that backup storage cannot be found or that a volume snapshot cannot be committed as an image.
• The error includes a PS UUID, volume snapshot UUID, or information about the target image.

Environment

• Product: ZVF
• Version: 4.x
• Component: ZSphere
• Affected object: virtual machine cloning
• Scenario: For migration and cloning issues, confirm the current version, deployment type, storage type, and operation timeline.

Possible causes

• Backup storage or image storage is disconnected, so the cloning process cannot create an intermediate image.
• The connection between the primary storage that contains the volume snapshot and the target image repository is abnormal.
• Historical snapshots, residual tasks, or abnormal storage status interrupt the cloning path.

Resolution

Perform the following checks in order, and record the affected object, occurrence time, complete error message, and current status.

1. Confirm that backup storage, image storage, and primary storage are online and have sufficient capacity.
2. Record the PS UUID, volume snapshot UUID, virtual machine UUID, and cloning task UUID in the error.
3. Check the failure stack trace for committing the snapshot to the image repository in the management service logs.
4. If residual tasks exist, first ask ZStack official technical support to confirm resource references to avoid directly deleting underlying snapshot or image objects.

Remediation

1. Restore the availability of backup storage, image storage, and primary storage, and ensure that target storage capacity meets cloning or image commit requirements.
2. After confirming that the volume snapshot is not referenced by other tasks, start cloning or image commit again. Ask ZStack official technical support to confirm the remediation path for residual tasks.

Verification

• The cloning task can be created normally, and the volume snapshot can be committed as an image.
• Task Center and management service logs no longer report that backup storage cannot be found or that snapshot commit failed.