Bug 1084970

Summary: [vdsm] getStorageDomainInfo fails due to key 'info' missing from poolInfo for master domain
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsmAssignee: Yoav Kleinberger <ykleinbe>
Status: CLOSED ERRATA QA Contact: Gadi Ickowicz <gickowic>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: abaron, acanan, adahms, amureini, bazulay, ederevea, fsimonce, gickowic, iheim, lpeer, mkalinin, nlevinki, sbonazzo, scohen, tnisan, yeylon
Target Milestone: ---Keywords: Reopened, ZStream
Target Release: 3.3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: vdsm-4.13.2-0.14.el6ev Doc Type: Bug Fix
Doc Text:
Previously, the getStorageDomainInfo action of the vdsClient command would fail when run under certain conditions. Now, the logic used to retrieve information on storage domains using the vdsClient command has been revised so that the action returns information correctly.
Story Points: ---
Clone Of: 1033942 Environment:
Last Closed: 2014-05-27 08:57:28 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:
Bug Depends On: 1033942    
Bug Blocks:    

Comment 1 Allon Mureinik 2014-04-21 15:12:07 UTC
*** Bug 1088974 has been marked as a duplicate of this bug. ***

Comment 3 Gadi Ickowicz 2014-05-07 13:45:28 UTC
verified on is36:

[root@purple-vds2 ~]# vdsClient -s 0 getStorageDomainInfo 1a091f8e-d4b7-4197-94d1-fc19e1e3c02b
        uuid = 1a091f8e-d4b7-4197-94d1-fc19e1e3c02b
        vguuid = rbYYcM-9TQJ-wAJw-Bawq-KS1V-P22k-KDOEnz
        lver = 0
        state = OK
        version = 3
        role = Master
        pool = ['5849b030-626e-47cb-ad90-3ce782d831b3']
        spm_id = 2
        type = ISCSI
        class = Data
        master_ver = 1
        name = ISCSI01

[root@purple-vds2 ~]# rpm -q vdsm
[root@purple-vds2 ~]# rpm -q vdsm-cli
[root@purple-vds2 ~]#

Comment 5 errata-xmlrpc 2014-05-27 08:57:28 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.