Bug 1391367 - WebUI:Tagvis - Cloud Key Pairs does not honor tag visibility
Summary: WebUI:Tagvis - Cloud Key Pairs does not honor tag visibility
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Marek Aufart
QA Contact: Dave Johnson
URL:
Whiteboard: ui:tag:cloud
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-03 08:01 UTC by Ramesh A
Modified: 2018-10-02 14:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:


Attachments (Terms of Use)

Description Ramesh A 2016-11-03 08:01:32 UTC
Description of problem:
Cloud Key Pairs does not honor tag visibility

Version-Release number of selected component (if applicable):
5.7.0.9-beta2.1.20161101182054_eb0afaa

How reproducible:
Very

Steps to Reproduce:
1. Manage a Cloud Provider
2. As Admin, Create a New Role will all the module access
3. As Admin, Create a New Group with the above role, assign a tag in "My Company Tags" (say Service Level - Gold) under "Assign Filters" section 
4. As Admin, Create a New User with the above created Group
5. As Admin, Navigate to Compute ==> Clouds ==> Key Pairs
6. Select a Key Pair ==> Click on the Policy button ==> Edit Tags ==> Assign the same tag which is used in Step 2 (for this example, Service Level - Gold)
7. Login as the newly created user, and check for the displayed Key Pairs

Actual results:
Displays all the key pairs despite the restriction

Expected results:
Should display only the key pairs based on "Tag Visibility" restriction

Additional info:

Comment 4 Josh Carter 2018-10-02 14:33:28 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 5 Josh Carter 2018-10-02 14:34:08 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 6 Josh Carter 2018-10-02 14:35:35 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!


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