Description of problem: For some reason we have not called disk finalized API, after the image inactivity timeout the transfer session is expired but the disk is not unlocked. Is there any way to unlock the disk without any user intervention. Version-Release number of selected component (if applicable): How reproducible: Frequent Steps to Reproduce: 1.Initiate Disk Transfer with inactivity timeout of 10 mins 2.Not call finalize API 3.After the timeout transfer session is expired, but disk is locked Actual results: After the timeout transfer session is expired, but disk is locked Expected results: After the timeout transfer session is expired, and the disk is also unlocked Additional info:
Daniel please have a look Marina, can you please comment on how to unlock the disk entity as a work around for the meanwhile?
Hi Guarav, Please check this KCS: https://access.redhat.com/solutions/396753. If you have further questions, you should open a support ticket via customer portal and we will help you.
(In reply to Marina Kalinin from comment #2) > Hi Guarav, > Please check this KCS: https://access.redhat.com/solutions/396753. > If you have further questions, you should open a support ticket via customer > portal and we will help you. Hi Guarav, Did this help? Do you have any feedback on this or can I close this? Best, Pavan.
Yes, this was helpful. I was hoping to know if the disk can be unlocked automatically after the timeout.
Anyways, you can close this.
ovirt-imageio-daemon does not control disk state, this is engine bug.
This bug/RFE didn't get enough attention so far and is now flagged as pending close. Please review if it is still relevant and provide additional details/justification/patches if you believe it should get more attention for the next oVirt release.
This bug didn't get any attention in a long time, and it's not planned in foreseeable future. oVirt development team has no plans to work on it. Please feel free to reopen if you have a plan how to contribute this feature/bug fix.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days