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

Bug 1668722

Summary:	CinderLib - Storage Domain name not showing in the disk list of Managed Block type
Product:	[oVirt] ovirt-engine	Reporter:	Fred Rolland <frolland>
Component:	BLL.Storage	Assignee:	Eyal Shenitzky <eshenitz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shir Fishbain <sfishbai>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs
Target Milestone:	ovirt-4.3.1	Flags:	rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-13 16:40:31 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:
Bug Blocks:	1539837

Description Fred Rolland 2019-01-23 12:41:56 UTC

Description of problem:
Storage Domain name not showing in the disk list of Managed Block type

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

How reproducible:
100%

Steps to Reproduce:
1. Create a Managed Block Storage disk
2. Go the disks list
3. Select "Managed Block" filter button

Actual results:
The "Storage Domain" column is empty

Expected results:

The "Storage Domain" column display the SD of the disk.

Additional info:

Comment 1 Shir Fishbain 2019-03-07 14:35:25 UTC

Verified
The "Storage Domain" column displays the SD of the disks

cinderlib version : 0.3.9
ovirt-engine-4.3.1.1-0.1.el7.noarch
vdsm-4.30.9-1.el7ev.x86_64

Comment 2 Sandro Bonazzola 2019-03-13 16:40:31 UTC

This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.