Bug 1533596 - Backport: Fixed Dell EMC VMax driver parameter typo
Summary: Backport: Fixed Dell EMC VMax driver parameter typo
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-cinder
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z5
: 11.0 (Ocata)
Assignee: Alan Bishop
QA Contact: Avi Avraham
URL:
Whiteboard:
Depends On: 1527222
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-11 17:37 UTC by Rajini Karthik
Modified: 2019-02-17 03:28 UTC (History)
26 users (show)

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.
Clone Of:
Environment:
Last Closed: 2018-05-18 17:08:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 532927 0 None None None 2018-02-20 15:11:47 UTC
Red Hat Product Errata RHBA-2018:1622 0 None None None 2018-05-18 17:09:49 UTC

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
Note You need to log in before you can comment on or make changes to this bug.