Bug 1096508

Summary: VDSM report that snapshot status ok even though snapshot status is BROKEN according to engine
Product: Red Hat Enterprise Virtualization Manager Reporter: Raz Tamir <ratamir>
Component: vdsmAssignee: Daniel Erez <derez>
Status: CLOSED DUPLICATE QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: amureini, bazulay, derez, gklein, iheim, lpeer, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-15 15:01:44 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:
Attachments:
Description Flags
vdsm and engine logs none

Description Raz Tamir 2014-05-11 12:05:48 UTC 
Created attachment 894417 [details]
vdsm and engine logs

Description of problem:
After got the same result as this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1082655, VDSM report that the snapshot volume is ok:

vdsClient -s 0 getVolumeInfo 0bc6332d-286e-470c-bbd3-e7b394b32d28 `vdsClient -s 0 getConnectedStoragePoolsList` ae9591b7-0471-4c5c-84f1-4cdb2325eb5e 6b40aa16-f356-4a1d-ae14-c76f9683062d
        status = OK
        domain = 0bc6332d-286e-470c-bbd3-e7b394b32d28
        capacity = 6442450944
        voltype = LEAF
        description =
        parent = 58e7906d-acf8-4ff6-8163-cbfb3ed7ecc6
        format = COW
        image = ae9591b7-0471-4c5c-84f1-4cdb2325eb5e
        uuid = 6b40aa16-f356-4a1d-ae14-c76f9683062d
        disktype = 2
        legality = LEGAL
        mtime = 1399807653
        apparentsize = 1073741824
        truesize = 1073741824
        type = SPARSE
        children = []
        pool =
        ctime = 1399807653



Version-Release number of selected component (if applicable):
vdsm-4.14.7-0.2.rc.el6ev.x86_64
rhevm-3.4.0-0.16.rc.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Block connection from host to storage right after snapshot deletion
2. After ~10 minutes snapshot status --> BROKEN
3. Check snapshot volume with vdsClient

Actual results:
VDSM report that snapshot is ok

Expected results:
should be BROKEN

Additional info:
Comment 1 Allon Mureinik 2014-05-12 17:34:54 UTC 
Daniel, AFAIK, the status in the GUI is the status of a VM snapshot. In that case, this is documentation bug, if anything.

Can you please confirm/refure?
Comment 2 Daniel Erez 2014-05-15 15:01:44 UTC 
(In reply to Allon Mureinik from comment #1)
> Daniel, AFAIK, the status in the GUI is the status of a VM snapshot. In that
> case, this is documentation bug, if anything.
> 
> Can you please confirm/refure?

Indeed, broken VM snapshot is merely an engine terminology; i.e. vdsm isn't aware (and shouldn't be) of this status. In any case, broken status should be removed as part of bug 1056935.

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