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

Bug 1321444

Summary: [z-stream clone] Storage activities are failing with error "Image is not a legal chain"
Product: Red Hat Enterprise Virtualization Manager Reporter: Allon Mureinik <amureini>
Component: vdsmAssignee: Adam Litke <alitke>
Status: CLOSED ERRATA QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: urgent    
Version: 3.6.3CC: acanan, adevolder, alitke, amureini, bazulay, cshao, ebenahar, fdeutsch, gklein, gwatson, huiwa, huzhao, jcoscia, kmashalk, leiwang, lsurette, mkalinin, nashok, nsoffer, obockows, pdwyer, weiwang, yaniwang, ycui, yeylon, ykaul, ylavi
Target Milestone: ovirt-3.6.4Keywords: Regression, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1319987 Environment:
Last Closed: 2016-04-04 01:17:59 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: 1319987    
Bug Blocks:    

Comment 3 Elad 2016-03-28 12:29:33 UTC
Tested the following scenario:

1) Created a VM with block storage based disk attached 
2) Started the VM on a non SPM host
3) Selected the host where the VM was running to be SPM
4) Stopped the VM and tried to perform storage operations like template creation and disk extension

Storage operations succeeded.

Tested using the following:
vdsm-4.17.23.2-1.el7ev.noarch
libvirt-daemon-1.2.17-13.el7_2.4.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.10.x86_64
rhevm-3.6.4.1-0.1.el6.noarch


Tested also over the following where the issue reproduced ("Image is not a legal chain"):
vdsm-4.17.23.1-0.el7ev.noarch
rhevm-3.6.4-0.1.el6.noarch

Comment 5 errata-xmlrpc 2016-04-04 01:17:59 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-2016:0586