Skip to content

Volume Migration Stuck in "Migrating" State #10801

Closed Answered by nxsbi
kanagarajb0720 asked this question in Q&A
Discussion options

You must be logged in to vote

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.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by DaanHoogland
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #10798 on May 01, 2025 06:38.