Bug 1450525

Summary: Cannot select placement for Cloud Volumes (openstack cinder storage provider) and this volumes are created in different tenants during provisioning of the instance.
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvidersAssignee: Sam Lucidi <slucidi>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: high Docs Contact:
Priority: high    
Version: 5.7.0CC: cpelland, dajohnso, fdewaley, gekis, jfrey, jhardy, obarenbo, opavlenk, simaishi, tzumainn
Target Milestone: GAKeywords: ZStream
Target Release: 5.7.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: openstack:volume:provision:tenant
Fixed In Version: 5.7.3.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1449915 Environment:
Last Closed: 2017-06-28 15:03:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Embargoed:
Bug Depends On: 1449915    
Bug Blocks:    

Comment 2 CFME Bot 2017-05-12 22:26:22 UTC 
New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/6075fe69fa0537ddf07c635a4669e837b3a31d2c

commit 6075fe69fa0537ddf07c635a4669e837b3a31d2c
Author:     tzumainn <tzumainn>
AuthorDate: Thu May 11 15:33:07 2017 -0400
Commit:     Satoe Imaishi <simaishi>
CommitDate: Fri May 12 18:21:23 2017 -0400

    Merge pull request #33 from mansam/provision-volumes-in-same-tenant-as-vm
    
    Provision VM-attached volumes in the same tenant as the VM
    (cherry picked from commit 1c4ed0b530268a9964b846a4e60a862d2b55a510)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1450525

 .../providers/openstack/cloud_manager/provision/volume_attachment.rb | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
Comment 4 Ido Ovadia 2017-06-15 16:25:46 UTC 
Verified
========
5.7.3.1
Comment 6 errata-xmlrpc 2017-06-28 15:03:41 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/RHSA-2017:1601