Bug 1469440 - Request for including an upstream fix(466514/) for emc vnx volume driver
Summary: Request for including an upstream fix(466514/) for emc vnx volume driver
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 11.0 (Ocata)
Assignee: Eric Harney
QA Contact: Avi Avraham
URL:
Whiteboard:
Depends On: 1465119
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-11 09:33 UTC by Peter Wang
Modified: 2017-09-13 21:49 UTC (History)
3 users (show)

Fixed In Version: openstack-cinder-10.0.3-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-13 21:49:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2715 0 normal SHIPPED_LIVE openstack-cinder bug fix advisory 2017-09-14 01:46:36 UTC

Description Peter Wang 2017-07-11 09:33:31 UTC 
Description of problem:

VNX driver should use the `state_path` instead of home of current
user, or we may meet permission error when creating folder for storing
data.

Version-Release number of selected component (if applicable):
RedHat Openstack 11(Ocata)

How reproducible:


Steps to Reproduce:
1. configure VNX driver as cinder backend
2. restart cinder volume
3.

Actual results:

Driver failed to start as permission denied

Expected results:
the driver can start up normally.

Additional info:

This is already fixed and backported to ocata

https://review.openstack.org/#/c/466514/
Comment 1 Eric Harney 2017-07-11 13:37:34 UTC 
This will be included in the 10.0.3 openstack-cinder build.
Comment 2 Lily Jing 2017-07-26 07:40:44 UTC 
(In reply to Eric Harney from comment #1)
> This will be included in the 10.0.3 openstack-cinder build.

Eric,

Any ETA of the build?
Comment 6 errata-xmlrpc 2017-09-13 21:49:37 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-2017:2715
Note You need to log in before you can comment on or make changes to this bug.