Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1984000

Summary:	disk remained locked after throwing nullpointerexception
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Marian Jankular <mjankula>
Component:	ovirt-engine	Assignee:	Eyal Shenitzky <eshenitz>
Status:	CLOSED DUPLICATE	QA Contact:	Avihai <aefrat>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.4.5	CC:	aefrat, bzlotnik, nsoffer, rhodain
Target Milestone:	---
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-07-21 14:20:08 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:

Description Marian Jankular 2021-07-20 11:46:47 UTC

Description of problem:
disk remained locked after successful snapshot removal (previous snapshot removal failed however only in engine while it was successful on the host)

Version-Release number of selected component (if applicable):
RHV 4.4.5

How reproducible:
2 times in customer environment

Steps to Reproduce:
1. initial snapshot deletion does fail in the engine but not in the host
2.
3.

Actual results:
disk remains locked


Expected results:
disk will be unlocked

Additional info:
will add logs

Comment 2 Nir Soffer 2021-07-21 13:52:10 UTC

> initial snapshot deletion does fail in the engine but not in the host

So this happens after delete snapshot completed successfully on the host,
but fail on engine?

Is this from a delete snapshot stress test, or from general usage in
production?

Comment 3 Benny Zlotnik 2021-07-21 13:58:01 UTC

stack trace and time of failure suggest this is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1956677

Comment 4 Benny Zlotnik 2021-07-21 14:20:08 UTC


*** This bug has been marked as a duplicate of bug 1956677 ***

Comment 5 Marian Jankular 2021-07-22 07:20:26 UTC

this issue is from general production use