Despite the query didn't show anything , I tried the unlock and the engine released it, so I removed it and created a smaller disk (and later extended). My guess is that the underlying storage is too slow, but this is not the real issue. I'm more interested why: 1. The engine didn't clean it up itself - after all , no mater the reason, the operation has failed? 2. Why the query fail to see the disk , but I have managed to unlock it? Best Regards, Strahil Nikolov В понеделник, 20 април 2020 г., 17:45:11 Гринуич+3, Benny Zlotnik <bzlotnik@redhat.com> написа: anything in the logs (engine,vdsm)? if there's nothing on the storage, removing from the database should be safe, but it's best to check why it failed On Mon, Apr 20, 2020 at 5:39 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:

Hello All,

did anyone observe the following behaviour:

1. Create a new disk from the VM -> disks UI tab 2. Disk creation failes , but stays in locked state 3. Gluster storage has no directory with that uuid 4. /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh doesn't find anything: [root@engine ~]# /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -q -t all

Locked VMs

Locked templates

Locked disks

Locked snapshots

Illegal images

Should I just delete the entry from the DB or I have another option ?

Best Regards, Strahil Nikolov

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6E4RJM7I3BT33C...