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:
Zita, Can you add missing tagging support for Ansible Tower Providers. Let me know if you have questions. Thanks, ~Harpreet
Confirmed this is still an issue in 4.2. I will check 4.5 later tonight / over the weekend.
Hi, is a provider under Configuration -> Management -> Providers (a Foreman provider)supposed to have tags or Ansible Tower? Or both? Thanks, Zita
https://github.com/ManageIQ/manageiq-ui-classic/pull/1534
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.
Can add the tag to the Ansible Tower Provider with Policy button in Automate->Ansible Tower-> Explorer. Verified in 5.9.0.2
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