Newly uploaded disk stuck in 'Finalizing Failure' status
Hey there, A few days ago, I tried to create a new template using one of the Ansible playbooks I frequently use. This time, the upload of the disk failed, possibly due to an unrelated error. The disk is now stuck in Ovirt. It has the status 'Finalizing Failure' and it's locked, thus I cannot remove it. Trying to unlock the disk with the 'unlock_entity.sh' helper utility does not help. The utility says it has completed it task successfully but the disk remains in this state. I decided to check the logs, and see that `engine.log` gets spammed with these lines every 10 seconds ``` 2021-03-03 09:05:38,335Z WARN [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-45) [redacted] Failed to stop image transfer session. Ticket does not exist for image '[disk uuid]' ``` How can I force Ovirt to remove this disk? I presume the upload failure itself is a different error, possibly related to our setup. Hence this is not the topic of this thread. I just want to know how I can remove these disks. Thanks, Nick
On Wed, Mar 03, 2021 at 09:08:25AM -0000, n.bouwhuis@speakup.nl wrote:
Hey there,
A few days ago, I tried to create a new template using one of the Ansible playbooks I frequently use. This time, the upload of the disk failed, possibly due to an unrelated error.
The disk is now stuck in Ovirt. It has the status 'Finalizing Failure' and it's locked, thus I cannot remove it. Trying to unlock the disk with the 'unlock_entity.sh' helper utility does not help. The utility says it has completed it task successfully but the disk remains in this state.
I don't know if it will still work after running the unlock tool, but normally you should be able to cancel the operation (Storage -> Disks -> Transfer -> Cancel). Or was that operation grayed out? Tomas
I decided to check the logs, and see that `engine.log` gets spammed with these lines every 10 seconds
``` 2021-03-03 09:05:38,335Z WARN [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-45) [redacted] Failed to stop image transfer session. Ticket does not exist for image '[disk uuid]' ```
How can I force Ovirt to remove this disk?
I presume the upload failure itself is a different error, possibly related to our setup. Hence this is not the topic of this thread. I just want to know how I can remove these disks.
Thanks, Nick _______________________________________________ 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/OE5DYCK67D2URO...
-- Tomáš Golembiovský <tgolembi@redhat.com>
On Wed, Mar 03, 2021 at 09:08:25AM -0000, n.bouwhuis(a)speakup.nl wrote:
I don't know if it will still work after running the unlock tool, but normally you should be able to cancel the operation (Storage -> Disks -> Transfer -> Cancel). Or was that operation grayed out?
Tomas Yep. That option is grayed out unfortunately. The only available option under the Transfer menu is 'Start', funnily enough.
On Wed, Mar 3, 2021 at 11:38 AM <n.bouwhuis@speakup.nl> wrote:
On Wed, Mar 03, 2021 at 09:08:25AM -0000, n.bouwhuis(a)speakup.nl wrote:
I don't know if it will still work after running the unlock tool, but normally you should be able to cancel the operation (Storage -> Disks -> Transfer -> Cancel). Or was that operation grayed out?
Tomas Yep. That option is grayed out unfortunately. The only available option under the Transfer menu is 'Start', funnily enough.
Please file a bug for this. Engine should get stuck in an endless loop, and it should be possible to cancel the operation from the UI. In the past we did not have the necessary support on the host for this, but now it is easy to add. To get rid of the stuck transfer, you need to remove it from the db manually. Find it in the image_transfers table, and delete it. You may also need to change the imagestatus of the related disk from 2 (Locked) to 1 (OK) in the images table. I hope Benny can provide more detailed instructions tomorrow. Nir
participants (3)
-
n.bouwhuis＠speakup.nl -
Nir Soffer -
Tomáš Golembiovský