Bug 1378603 - Ansible Tower Job Templates changes are not picked up when refreshing an Ansible Tower provider in CloudForms
Summary: Ansible Tower Job Templates changes are not picked up when refreshing an Ansi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.7.0
Assignee: Brandon Dunne
QA Contact: Pavol Kotvan
URL:
Whiteboard: tower:ems_refresh:retest
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 21:20 UTC by Jerome Marc
Modified: 2018-03-29 15:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-17 15:21:11 UTC
Category: ---
Cloudforms Team: Ansible
Target Upstream Version:


Attachments (Terms of Use)
Screenshot showing Provider Refresh / Not Refresh Scenarios (179.95 KB, image/png)
2016-09-29 17:10 UTC, Jerome Marc
no flags Details

Description Jerome Marc 2016-09-22 21:20:52 UTC
Description of problem:
Changes in Ansible Tower on job templates are not updated in CloudForms despite an Ansible Tower refresh.

Version-Release number of selected component (if applicable):
5.6.1.2.20160810181333_8ba817b

How reproducible:
Always

Steps to Reproduce:
1. Setup an Ansible Tower provider in CloudForms and refresh Relationships and Power States
2. In Ansible Tower, modify the name of an Ansible Job Template
3. Refresh Relationships and Power States again in CloudForms

Actual results:
The Ansible Job Template's name never gets updated in CloudForms.

Expected results:
Name should be updated.

Additional info:
This create an incoherent state between the two products.

Comment 2 Jerome Marc 2016-09-22 21:25:49 UTC
After further testing, this BZ is related to Bug 1378602 - Deletion not possible from within Ansible Tower Configuration Provider view

Basically the action under the Button configuration on the Ansible Tower provider view do not work. Hence my refresh never being actioned.

When going back a level under Ansible Tower providers in the tree and selecting the provider, the click of Configuration > Refresh... does trigger a refresh and the Ansible Tower Job Template gets updated.

Comment 5 Jerome Marc 2016-09-29 17:10:37 UTC
Created attachment 1205988 [details]
Screenshot showing Provider Refresh / Not Refresh Scenarios

Comment 6 Dave Johnson 2016-09-29 23:48:24 UTC
Pavol, can you reproduce this please and share the environment with dev.

Comment 7 Pavol Kotvan 2016-10-04 07:52:21 UTC
Re-tested this on 5.6.1.2.20160810181333_8ba817b appliance with Tower 3.0.1 and 2.4.3. I confirm there is definitely problem as stated in comment #2.

The problem is that refresh of Tower provider does not work when it is performed from accordion tree:
Navigate to Config management, click on Providers in accordion tree, Ansible Tower providers, select your Tower provider (in accordion tree), click on Configuration button and perform refresh of provider. 
When Tower provider is selected from "All Ansible Tower Providers" page and are refreshed, everything is working as expected.

Comment 8 Brandon Dunne 2016-10-13 20:56:32 UTC
Hi Pavol,

I tested on master, 5.7 and 5.6.2.1 both by checking the box on the right and by selecting the manager in the tree on the left and everything is working for me.  Can you confirm that it is working on 5.6.2.1?

Thanks,
Brandon

Comment 9 Pavol Kotvan 2016-10-17 10:42:42 UTC
Hi Brandon,
I confirm this works as expected in 5.6.2.1.20160922130607_92d5b5e build.
Pavol

Comment 10 Brandon Dunne 2016-10-17 15:21:11 UTC
Closing since this works on the latest build of the 5.6 z-stream.


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