You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Volume Migration Stuck in "Migrating" State #10798
We initiated a volume migration from one primary storage to another. Although the migration started, the volume has remained in the "Migrating" state for the past four days. Additionally, a new volume creation is stuck in the "Creating" state. Although the job was canceled, the original volume still shows as "Migrating," and the new volume remains in "creating".
To move forward, how can we update the status of the affected volume from "Migrating" to "Ready" in the database.
versions
ACS version: 4.19.1.3
Hypervisor: XenServer
Storage: Pure Storage
The good thing with migrations is that the existing volume does not get touched until there is successful migration completion.
Without knowing why it was stuck, if your goal is to set the status correctly, you need to write manual update statements in the database.
For the current active volume (check your vm to make sure)
Update volumes
Set status=‘Ready’
Where I’d = x.
For the one that failed
Update volumes
Set status=‘Expunged’
Where I’d = y.
Then also check the install_path for the failed one as you may have to manually delete the file if partial file was moved.
Activity
nxsbi commentedon May 1, 2025
The good thing with migrations is that the existing volume does not get touched until there is successful migration completion.
Without knowing why it was stuck, if your goal is to set the status correctly, you need to write manual update statements in the database.
For the current active volume (check your vm to make sure)
Update volumes
Set status=‘Ready’
Where I’d = x.
For the one that failed
Update volumes
Set status=‘Expunged’
Where I’d = y.
Then also check the install_path for the failed one as you may have to manually delete the file if partial file was moved.