Bug 1449915 - Cannot select placement for Cloud Volumes (openstack cinder storage provider) and this volumes are created in different tenants during provisioning of the instance.
Summary: Cannot select placement for Cloud Volumes (openstack cinder storage provider)...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.0
Assignee: Sam Lucidi
QA Contact: Ido Ovadia
URL:
Whiteboard: openstack:volume:provision:tenant
Depends On:
Blocks: 1450220 1450525
TreeView+ depends on / blocked
 
Reported: 2017-05-11 07:13 UTC by ITD27M01
Modified: 2020-07-16 09:33 UTC (History)
10 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1450220 1450525 (view as bug list)
Environment:
Last Closed: 2018-03-06 15:45:19 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description ITD27M01 2017-05-11 07:13:13 UTC
Description of problem:
Cloud volumes do not fall under the restriction of cloud tenants. The user can perform any CRUD-operations on the cloud volumes in any cloud tenant not only in users own.

Moreover, when you deploy cloud instances (Lifecycle->Provisioning) and choose an additional volume to provision it provisioned in any cloud tenant (Likely to be selected first.) other than the tenant of provisioned instance.

Version-Release number of selected component (if applicable):
[root@srv-os-cfme02 vmdb]# cat VERSION 
5.7.2.1

RHOSP 10 (Newton)

How reproducible:


Steps to Reproduce:
1. Add OpenStack Cloud Provider keystone v3 with cloud tenant sync.
2. Create projects for diffirent users groups in OpenStack.
3. Add users groups to CFME and assign cfme tenants to them.
4. Start provisioning cloud instance with additional volume (Lifecycle->Provisioning)

Actual results:

Cloud volume provisioned in any cloud tenant (likely to be selected first) other than the tenant of provisioned instance.
Expected results:
Cloud volume provisioned in the same cloud tenant as the tenant of provisioned instance. And :volumes options hash have placement option for cloud tenant selection.

Additional info:

Comment 6 Ido Ovadia 2018-02-14 13:45:04 UTC
Verified
========
5.9.0.20


Note You need to log in before you can comment on or make changes to this bug.