Bug 1391367

Summary:	WebUI:Tagvis - Cloud Key Pairs does not honor tag visibility
Product:	Red Hat CloudForms Management Engine	Reporter:	Ramesh A <rananda>
Component:	UI - OPS	Assignee:	Marek Aufart <maufart>
Status:	CLOSED WONTFIX	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.7.0	CC:	dajohnso, hkataria, jhardy, mpovolny, obarenbo
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ui:tag:cloud
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Openstack	Target Upstream Version:

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!