Bug 1436846 – Unable to apply tag to Ansible Tower Providers

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1436846 - Unable to apply tag to Ansible Tower Providers

Summary:	Unable to apply tag to Ansible Tower Providers

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	UI - OPS (Show other bugs)
Sub Component:
Version:	5.6.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	GA
Target Release:	5.9.0
Assigned To:	Zita Nemeckova
QA Contact:	Kedar Kulkarni
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-28 16:05 EDT by Lynn Dixon
Modified:	2018-03-01 08:11 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	5.9.0.1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-03-01 08:11:02 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:0380	normal	SHIPPED_LIVE	Moderate: Red Hat CloudForms security, bug fix, and enhancement update	2018-03-01 13:37:12 EST

Groups: None (edit)

Description Lynn Dixon 2017-03-28 16:05:17 EDT

Description of problem:
Cloudforms does not have the ability to apply a tag to an Ansible Tower Provider so that RBAC can be utilized.  This means that when a user has a tag filter applied to their group, they cannot see any of the Ansible Tower Providers.

Version-Release number of selected component (if applicable):
cfme-5.6.2.2-1.el7cf.x86_64

How reproducible:
Use a standard deployment of Cloudforms 4.1 (cfme-5.6.2.2-1.el7cf.x86_64)

Steps to Reproduce:
1. Navigate to Configuration -> Configuration Management -> Providers 
2. Select an existing Ansible Tower Provider (or add a new one)
3. Notice there is no "Policy" button to apply a tag to the provider

Actual results:
Can't apply any tags to Tower Providers

Expected results:
Ability to Tag a Tower provider so that they are visible to users that have a tag filter applied to their group.

Additional info:

Comment 2 Harpreet Kataria 2017-03-28 23:31:55 EDT

Zita,

Can you add missing tagging support for Ansible Tower Providers. Let me know if you have questions.

Thanks,
~Harpreet

Comment 3 Lynn Dixon 2017-06-02 12:28:18 EDT

Confirmed this is still an issue in 4.2.   I will check 4.5 later tonight / over the weekend.

Comment 4 Zita Nemeckova 2017-06-06 10:56:25 EDT

Hi,

is a provider under Configuration -> Management -> Providers (a Foreman provider)supposed to have tags or Ansible Tower? Or both?

Thanks,
Zita

Comment 5 Zita Nemeckova 2017-06-13 08:06:11 EDT

https://github.com/ManageIQ/manageiq-ui-classic/pull/1534

Comment 6 Lynn Dixon 2017-06-19 11:16:53 EDT

Zita,
In response to your question in comment 4, I would hope that we could apply tags to any configuration provider so that RBAC can be used to filter who can see and work with these providers.

Comment 7 Kedar Kulkarni 2017-10-12 14:02:06 EDT

Can add the tag to the Ansible Tower Provider with Policy button in Automate->Ansible Tower-> Explorer.
Verified in 5.9.0.2

Comment 10 errata-xmlrpc 2018-03-01 08:11:02 EST

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-2018:0380

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