Bug 1701244

Summary:	Disk not unlocked after inactivity timeout
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gaurav Jadhav <gauravjadhav.jadhav>
Component:	ovirt-engine	Assignee:	Pavel Bar <pbar>
Status:	CLOSED DEFERRED	QA Contact:	meital avital <mavital>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.1.0	CC:	abhay.marode, eshenitz, jeokim, michal.skrivanek, mkalinin, mtessun, nsoffer, pravin.amin, Sohail.Kazi, tnisan, usurse
Target Milestone:	---	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-29 11:33:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1691340, 1709496

Description Gaurav Jadhav 2019-04-18 13:32:27 UTC

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:

Comment 1 Tal Nisan 2019-04-22 13:28:40 UTC

Daniel please have a look
Marina, can you please comment on how to unlock the disk entity as a work around for the meanwhile?

Comment 2 Marina Kalinin 2019-04-22 14:20:59 UTC

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.

Comment 3 Pavan Chavva 2019-05-13 17:36:21 UTC

(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.

Comment 6 Gaurav Jadhav 2019-05-14 05:47:30 UTC

Yes, this was helpful.

I was hoping to know if the disk can be unlocked automatically after the timeout.

Comment 7 Gaurav Jadhav 2019-05-14 05:48:24 UTC

Anyways, you can close this.

Comment 15 Nir Soffer 2020-04-26 01:22:02 UTC

ovirt-imageio-daemon does not control disk state, this is engine bug.

Comment 20 Eyal Shenitzky 2021-08-31 05:58:19 UTC

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.

Comment 21 Michal Skrivanek 2021-09-29 11:33:06 UTC

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.

Comment 22 Red Hat Bugzilla 2023-09-18 00:16:00 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days