Bug 1629129

Summary: Cannot add Ansible Tower or refresh already added Ansible Tower
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvidersAssignee: Bronagh Sorota <bsorota>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: high Docs Contact:
Priority: high    
Version: 5.9.3CC: dmetzger, gblomqui, jfrey, jhardy, nachandr, obarenbo
Target Milestone: GAKeywords: ZStream
Target Release: 5.9.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.9.5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1621885 Environment:
Last Closed: 2018-11-05 13:59:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On: 1621885    
Bug Blocks:    

Comment 2 CFME Bot 2018-09-17 18:29:11 UTC 
New commit detected on ManageIQ/manageiq-providers-ansible_tower/gaprindashvili:

https://github.com/ManageIQ/manageiq-providers-ansible_tower/commit/762b1b3d2b4c243704fed6193f8a9bc09bb09dde
commit 762b1b3d2b4c243704fed6193f8a9bc09bb09dde
Author:     Adam Grare <agrare>
AuthorDate: Thu Sep  6 12:55:24 2018 -0400
Commit:     Adam Grare <agrare>
CommitDate: Thu Sep  6 12:55:24 2018 -0400

    Merge pull request #123 from jeffwarnica/handleNoUsernameInCreds

    Deal with ansible not having a username
    (cherry picked from commit 8bdd0d0d02286aaf1b28bd51765d3d4600cef1c9)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1629129

 app/models/manageiq/providers/ansible_tower/shared/inventory/parser/automation_manager.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Comment 3 Nandini Chandra 2018-10-03 22:43:25 UTC 
Unable to reproduce the issue locally without fix.

Marking the BZ as VERIFIED since the fix resolved the issue for the customer.
Comment 5 errata-xmlrpc 2018-11-05 13:59:33 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:3466