Bug 1730436

Summary:	Snapshot creation was successful, but snapshot remains locked
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gordon Watson <gwatson>
Component:	ovirt-engine	Assignee:	Benny Zlotnik <bzlotnik>
Status:	CLOSED ERRATA	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.8-4	CC:	gveitmic, mavital, nsimsolo, pelauter, smaudet, tnisan
Target Milestone:	ovirt-4.4.0	Keywords:	ZStream
Target Release:	4.3.6	Flags:	lsvaty: testing_plan_complete-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.6.1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1744507 (view as bug list)		Environment:
Last Closed:	2020-08-04 13:19:49 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:	1744507

Description Gordon Watson 2019-07-16 17:55:24 UTC

Description of problem:

Snapshot creation seemingly completed successfully, yet the snapshot remained 'LOCKED'. 

This VM consisted of two disks, each with three volumes, prior to the snapshot creation. The new volume for both disks was then successfully created and linked to each volume chain, marked as LEAF and set as the writable volume by 'qemu-kvm'.

All volume chains (d/b, volume metadata, XML, qcow headers) reflected the newly-added volumes correctly.

There were no tasks, jobs, steps or command entities in the d/b by the time it was captured.

It looks like the snapshot creation was successful, other than the snapshot (snapshots table entry) being unlocked.


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

RHV 4.2.8
RHEL 7.6 hosts
  vdsm-4.30.13-4 (VM host)
  vdsm-4.20.47-1 (SPM)


How reproducible:

Not.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 8 Benny Zlotnik 2019-07-24 08:23:23 UTC

Yep, reproduced successfully

Steps to reproduce for QE, similar to [1]
1. Place a sleep in /usr/lib/python2.7/site-packages/vdsm/API.py Volume#getInfo() for about 90 seconds
2. Reduce transaction timeout to 60 seconds (see [1] for instructions)
3. Create a live snapshot




[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1590218#c15

Comment 9 RHV bug bot 2019-08-08 13:17:32 UTC

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.3.z': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.3.z': '?'}', ]

For more info please contact: rhv-devops

Comment 10 RHV bug bot 2019-08-15 14:04:58 UTC

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.3.z': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.3.z': '?'}', ]

For more info please contact: rhv-devops

Comment 12 Daniel Gur 2019-08-28 13:11:41 UTC

sync2jira

Comment 13 Daniel Gur 2019-08-28 13:15:53 UTC

sync2jira

Comment 15 Nisim Simsolo 2019-11-18 15:43:46 UTC

verification builds:
ovirt-engine-4.4.0-0.4.master.el7
vdsm-4.40.0-141.gitb9d2120.el8ev.x86_64
qemu-kvm-3.1.0-30.module+el8.0.1+3755+6782b0ed.x86_64
libvirt-5.0.0-12.module+el8.0.1+3755+6782b0ed.x86_64
sanlock-3.8.0-2.el8.x86_64

Verification scenario:
1. Place a sleep in /usr/lib/python2.7/site-packages/vdsm/API.py Volume#getInfo() for about 90 seconds
2. Reduce transaction timeout to 60 seconds (see [1] for instructions)
3. Create a live snapshot

Comment 17 RHV bug bot 2019-12-13 13:14:46 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 18 RHV bug bot 2019-12-20 17:44:33 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 19 RHV bug bot 2020-01-08 14:48:52 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 20 RHV bug bot 2020-01-08 15:15:48 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 21 RHV bug bot 2020-01-24 19:50:44 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 24 errata-xmlrpc 2020-08-04 13:19:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:3247