GitHub user nxsbi added a comment to the discussion: Volume Migration Stuck in 
"Migrating" State

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. 


GitHub link: 
https://github.com/apache/cloudstack/discussions/10801#discussioncomment-13001479

----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org

Reply via email to