Bug 1436846 - Unable to apply tag to Ansible Tower Providers
Summary: Unable to apply tag to Ansible Tower Providers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.0
Assignee: Zita Nemeckova
QA Contact: Kedar Kulkarni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-28 20:05 UTC by Lynn Dixon
Modified: 2018-03-01 13:11 UTC (History)
7 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 13:11:02 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Description Lynn Dixon 2017-03-28 20:05:17 UTC
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-29 03:31:55 UTC
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 16:28:18 UTC
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 14:56:25 UTC
Hi,

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

Thanks,
Zita

Comment 6 Lynn Dixon 2017-06-19 15:16:53 UTC
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 18:02:06 UTC
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 13:11:02 UTC
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.