Bug 1014508

Summary:	LMI_SystemStorageDevice should not associate LMI_VGStoragePool
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Safranek <jsafrane>
Component:	openlmi-storage	Assignee:	Jan Safranek <jsafrane>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Barry Donahue <bdonahue>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	bdonahue, qcai
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 09:18:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jan Safranek 2013-10-02 09:05:19 UTC

Description of problem:
LMI_SystemStorageDevice is association between CIM_System and CIM_LogicalDevice. It currently associates all CIM_StorageExtents to CIM_System (which is fine), but also LMI_VGStoragePool to CIM_System. But LMI_VGStoragePool is *not* subclass of CIM_LogicalDevice, so it should not appear in this association.

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

How reproducible:
always

Steps to Reproduce:
1. enumerate instances of LMI_SystemStorageDevice on system with a volume group

Actual results:
LMI_VGStoragePool of the volume groups is associated to CIM_System

Expected results:
Only CIM_StorageExtents  are associated to CIM_System

Comment 1 Jan Safranek 2013-10-03 07:05:43 UTC

Upstream fix: https://git.fedorahosted.org/cgit/openlmi-storage.git/commit/?id=c0af4338943bd0a2fb68d40b5f392023f66d4dde

Comment 2 Jan Safranek 2013-11-01 11:36:50 UTC

This is already done upstream, waiting for release.

Comment 4 Ludek Smid 2014-06-13 09:18:55 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.