Skip to content

SAM retry migration fails with Volume already exist #2382

Description

@geet-pf9

What steps did you take and what happened?

  1. Try to do a failure of sam migration with wrong backend or type selection
  2. Now retry migration

Migrations failed with -

I0904 07:47:33.255467 1 pure.go:177] Adding host ESXI-HOST-01 to group (matched IQN: iqn.1998-01.com.vmware:localhost.lab.platform9.horse:1073153936:64)
I0904 07:47:33.255471 1 pure.go:171] Checking host NVME-ESXI-01, iqns: [], wwns: []
2026/09/04 07:47:33 Creating target volume Sam-pure-automation-Hard-disk-1 (sanitized from: Hard disk 1) with size 10737418240 bytes (10 GB)
2026/09/04 07:47:33 StorageAcceleratedCopy XCOPY completed in 2s (total: 2s) for disk Hard disk 1
2026/09/04 07:47:34 failed to perform StorageAcceleratedCopy copy: failed to copy disk Hard disk 1 via StorageAcceleratedCopy: failed to create target volume Sam-pure-automation-Hard-disk-1: failed to create volume Sam-pure-automation-Hard-disk-1: Response code: 400, ResponeBody: [{"msg": "Volume already exists.", "ctx": "Sam-pure-automation-Hard-disk-1"}]
Image

Its not deleting the old volume and keeps it there which causes above issue.

What did you expect to happen?

Sam migration with retry should work

Environment

main

vCenter version

NA

Anything else you would like to add?

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions