HI
It looks like you might be updating the wrong volume id, with the state
Ready,
You can get the uuid of the volume in the UI
Here the ID mentioned is the uuid of the volume
[image: image.png]
mysql> select * from volumes where uuid='ID from above command'\G
Example
mysql> select * from volumes where
uuid='bc795579-eb10-466f-b1ae-b05f5c33b2be'\G
*************************** 1. row ***************************
* id: 2*
account_id: 1
domain_id: 1
pool_id: NULL
last_pool_id: NULL
mysql>update volumes set state='Ready' where id='ID marked in Bold ';
Please check if this works.
Thanks & Regards
Nischal
On Wed, Mar 6, 2024 at 9:26 PM <h.chi...@bestnetllc.co.jp> wrote:
> Hello community
>
> For this issue, I tried deleting all resources.
>
> 1. Delete host from Cloud Stack
>
> 2. Delete cluster from Cloud Stack
>
> 3. Delete the primary storage associated with the cluster from Cloud Stack
>
> There is a problem here as well; the volume that is locked during
> migration cannot be deleted, and the primary storage cannot be deleted
> either.
>
> I have tried changing the state of the locked ID in the SQL VOLUME table
> to Ready and deleting the record itself, but the locked volume continues to
> be displayed as "Migrating" on Cloud Stack. Masu.
>
> If anyone knows how to deal with this issue please let me know.
>
> thank you.
>
> -----Original Message-----
> From: h.chi...@bestnetllc.co.jp <h.chi...@bestnetllc.co.jp>
> Sent: Wednesday, March 6, 2024 1:55 AM
> To: users@cloudstack.apache.org
> Subject: RE: volume was locked forever as "migration in progress"
>
> Hi Nischal
> thank you for your reply.
>
> Following your advice, I changed the state of the target volume to "Ready"
> using MySQL Workbench.
>
> However, the problem persists.
> I'm guessing that the table that holds the key to the migration process is
> somewhere else.
>
> If anyone knows please let me know.
>
> thank you.
>
> -----Original Message-----
> From: Nischal P <nischalnisc...@gmail.com>
> Sent: Tuesday, March 5, 2024 1:45 AM
> To: users@cloudstack.apache.org
> Subject: Re: volume was locked forever as "migration in progress"
>
> Hi Hideyuki
>
> If the volume is stuck in Migration state, I suggest that you take a back
> up of DB before proceeding to the next step.
>
> 1. Please check if the volume is present in the source storage or the
> destination 2. Once its confirmed, please update the mysql database
>
> 3 .mysql> select id from volumes where name='NAME OF VOLUME';
>
> 4. mysql> update volumes set state='Ready' where id=ID; - ID you get here
> is from Step 3.
>
> Please perform these steps carefully.
>
>
> Thanks & Regards
> Nischal
>
>
> On Mon, Mar 4, 2024 at 9:49 PM <h.chi...@bestnetllc.co.jp> wrote:
>
> > Hello
> > I have already tried it, but the volume is still locked as before.
> >
> > Below is what I tried.
> > Systemctl restart cloudstack-management
> > vm.job.timeout=50
> > job.expire. minutes=50
> >
> > kvm.storage.offline.migration.wait=120
> >
> > kvm.storage.online.migration.wait=120
> >
> > mergeVirtualMachineWithVolume＝120
> >
> > mergewait=120
> >
> > job.cancel.threshold.minutes=5
> >
> > job.expire.minutes=5
> >
> > I am very confused about this event.
> > If anyone knows of an effective workaround, please let me know.
> >
> > Regards
> > Hideyuki.C
> >
> > -----Original Message-----
> > From: Kiran Chavala <kiran.chav...@shapeblue.com>
> > Sent: Monday, March 4, 2024 3:25 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: volume was locked forever as "migration in progress"
> >
> > Hi
> >
> > Currently there is no way to force cancel a struck async job.
> >
> > you have to restart the management service
> >
> > service cloudstack-management restart
> >
> > Regards
> > Kiran
> >
> > From: h.chi...@bestnetllc.co.jp <h.chi...@bestnetllc.co.jp>
> > Date: Monday, 4 March 2024 at 1:43 AM
> > To: users@cloudstack.apache.org <users@cloudstack.apache.org>
> > Subject: volume was locked forever as "migration in progress"
> > Hello community
> >
> >
> >
> > Do you know how to force cancel a stuck job?
> >
> >
> >
> > When the source KVM host went down during storage migration, the
> > volume was locked forever as "migration in progress".
> >
> >
> >
> > thank you.
> >
> >
> >
> >
>
>
