Bug 1533596

Summary:	Backport: Fixed Dell EMC VMax driver parameter typo
Product:	Red Hat OpenStack	Reporter:	Rajini Karthik <rajini.karthik>
Component:	puppet-cinder	Assignee:	Alan Bishop <abishop>
Status:	CLOSED ERRATA	QA Contact:	Avi Avraham <aavraham>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	11.0 (Ocata)	CC:	abishop, arkady_kanevsky, audra_cooper, cdevine, christopher_dearborn, david_paterson, dcadzow, dcain, eharney, jjoyce, jschluet, juwu, kurt_hey, mburns, morazi, pgrist, rajini.karthik, randy_perryman, scohen, slinaber, smerrow, sreichar, srevivo, sumedh_sathaye, tshefi, tvignaud
Target Milestone:	z5	Keywords:	FeatureBackport, Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-cinder-10.3.1-4.el7ost	Doc Type:	Bug Fix
Doc Text:	A typo in the puppet-cinder code that configures the VMAX Cinder back-end driver has been fixed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-18 17:08:29 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:
Embargoed:
Bug Depends On:	1527222
Bug Blocks:

Description Rajini Karthik 2018-01-11 17:37:21 UTC

Description of problem:

https://review.openstack.org/#/c/532567/

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Tzach Shefi 2018-05-07 06:57:55 UTC

Verified on:
puppet-cinder-10.4.0-1.el7ost.noarch

Notice I don't have access to VNX to actually test functionality. 
Verification solely based on checking code has landed in RPM. 

Looking good fix is in. 
vi /usr/share/openstack-puppet/modules/cinder/manifests/backend/dellemc_vmax_iscsi.pp
-> 

name   => $::cinder::params::pywbem_package_name,

Comment 7 errata-xmlrpc 2018-05-18 17:08:29 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-2018:1622