Bug 1358031

Summary: Missing zone configuration for Ansible Tower provider
Product: Red Hat CloudForms Management Engine Reporter: Jerome Marc <jmarc>
Component: ProvidersAssignee: Greg McCullough <gmccullo>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: jfrey, jhardy, jocarter, obarenbo
Target Milestone: GA   
Target Release: 5.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-21 14:30:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jerome Marc 2016-07-19 21:18:50 UTC 
Description of problem:
When adding a new Ansible Tower provider, users are not prompted for the zone the configuration provider should be added to. CF simply adds the new provider to the current zone (e.g. UI zone). However this zone doesn't necessarily provide 'Provider Inventory' role (e.g. UI zone). It is then impossible to refresh the provider relationships and power states.

Version-Release number of selected component (if applicable):
5.6.0.13.20160624114606_13a9153 

How reproducible:
Always

Steps to Reproduce:
1. Login in CF4.1 from a UI appliance (within a UI Zone)
2. Configure a new Ansible Tower connection
3. Try to refresh the relationships & power states

Actual results:
CF fails to refresh as the UI appliance/zone does not have a 'Provider Inventory' role.

Expected results:
It should be possible to select which Zone we want the Ansible Tower provider to be added to, similar to all infrastructure & cloud providers.

Additional info:
A workaround is to add the 'Provider Inventory' role to the current zone. This is not acceptable for production deployment.
Comment 2 Josh Carter 2016-07-21 14:30:03 UTC 

*** This bug has been marked as a duplicate of bug 1353015 ***