Bug 1312513 - No easy way to identitfy which tenant belongs to which security group
No easy way to identitfy which tenant belongs to which security group
Status: CLOSED DUPLICATE of bug 1312512
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
All All
unspecified Severity high
: GA
: 5.6.0
Assigned To: Dan Clarizio
Dave Johnson
Depends On:
  Show dependency treegraph
Reported: 2016-02-26 18:46 EST by Kevin Morey
Modified: 2016-02-26 18:47 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-26 18:47:15 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kevin Morey 2016-02-26 18:46:03 EST
Description of problem:
I did a POC this week for a customer where their openstack environment had approximately 50+ tenants. The problem is that by default all openstack tenants have a default security group called 'default'. The customer quickly got frustrated that they could tell from a list view of security groups which tenant belonged to each 'default' security group.  Please add a cloud_tenant column in the list view.

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

How reproducible:

Steps to Reproduce:
1. add an openstack provider that has multiple tenants
2. once the provider refresh is completed navigate to Clouds / Security Groups in CF
3. Attempt easily identify which security group maps to which tenants

Actual results:
we got a view of 50+ security groups all called default. The customer has to navigate to cloud_tenants and follow the relationship to figure out which default security group it belonged to.

Expected results:
Expected to see which tenant belonged to each openstack security group

Additional info:
Comment 2 Kevin Morey 2016-02-26 18:47:15 EST

*** This bug has been marked as a duplicate of bug 1312512 ***

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