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

Bug 1584993

Summary: [downstream clone - 4.2.5] The Active VM snapshots table entry does not exist for a specific VM
Product: Red Hat Enterprise Virtualization Manager Reporter: RHV bug bot <rhv-bugzilla-bot>
Component: ovirt-engineAssignee: Benny Zlotnik <bzlotnik>
Status: CLOSED ERRATA QA Contact: Kevin Alon Goldblatt <kgoldbla>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.8CC: bzlotnik, ebenahar, lsurette, lveyde, mkalinin, pbrilla, Rhev-m-bugs, srevivo, tnisan, ybenshim, ylavi
Target Milestone: ovirt-4.2.5Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1561052 Environment:
Last Closed: 2018-07-31 17:49:18 UTC Type: ---
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: 1561052, 1590292    
Bug Blocks:    

Description RHV bug bot 2018-06-01 06:20:02 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1561052 +++
======================================================================

Description of problem:

The 'Active VM' snapshot does not exist in the snapshots table in the database for a specific VM. The uuid does exist however in the 'vm_snapshot_id' fields of the active images for each disk of that VM.

A volume creation error occurred at the time when a snapshot was taken in which this uuid was generated as the Active VM snapshot id.


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

RHV 4.1.8
RHEL .4 hosts;
  vdsm-4.19.45-1.el7


How reproducible:

Not.


Steps to Reproduce:
1.
2.
3.

Actual results:



Expected results:


Additional info:

(Originally by Gordon Watson)

Comment 8 Tal Nisan 2018-06-14 08:50:55 UTC
Verification depends on bug 1590292, moving back to assigned until bug 1590292 is resolved

Comment 9 Yaniv Kaul 2018-06-15 08:32:27 UTC
(In reply to Tal Nisan from comment #8)
> Verification depends on bug 1590292, moving back to assigned until bug
> 1590292 is resolved

But bug 1590292 is targeted to 4.2.5, why is this one on 4.2.4?

Comment 10 Sandro Bonazzola 2018-06-15 12:15:59 UTC
This bug is not marked as blocker and we entered blocker only phase for 4.2.4.
Please consider re-targeting to 4.2.5.

Comment 11 Tal Nisan 2018-06-17 08:32:52 UTC
(In reply to Yaniv Kaul from comment #9)
> (In reply to Tal Nisan from comment #8)
> > Verification depends on bug 1590292, moving back to assigned until bug
> > 1590292 is resolved
> 
> But bug 1590292 is targeted to 4.2.5, why is this one on 4.2.4?

I wasn't sure if it will be fixed within the 4.2.4 timeline

Comment 13 Pavol Brilla 2018-06-21 09:48:15 UTC
Because of conversation in above comments I am removing this bug from 4.2.4 erratum, and moving back to MODIFIED to reverse automatic switch to ON_QA by ET engine

Comment 15 Sandro Bonazzola 2018-06-29 16:21:54 UTC
git tag --contains da8634cc193e439ea54420597699411c0bfcb4f0
ovirt-engine-4.2.4.1
ovirt-engine-4.2.4.2
ovirt-engine-4.2.4.3
ovirt-engine-4.2.4.4
ovirt-engine-4.2.4.5
ovirt-engine-4.2.5

Moving to QE, should be possible to test with 4.2.4 GA along with bug #1590292

Comment 20 Kevin Alon Goldblatt 2018-07-08 12:11:46 UTC
Verified with the following code:
----------------------------------------
ovirt-engine-4.2.5-0.1.el7ev.noarch
vdsm-4.20.33-1.el7ev.x86_64

Verified with the following scenario:
----------------------------------------
1. Create VM with disk
2. Block access to storage from host
3. Create snapshot - fails to create snapshot and the Active snapshot is still in tact
4. Unblock the access to the storage domain from the host
5. Create a new snapshot now >>>>> Works fine



Moving to VERIFIED

Comment 22 errata-xmlrpc 2018-07-31 17:49:18 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, 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/RHBA-2018:2318