New commit detected on ManageIQ/manageiq-providers-ansible_tower/hammer:
Author: Jason Frey <email@example.com>
AuthorDate: Thu Jan 23 10:21:02 2020 -0500
Commit: Jason Frey <firstname.lastname@example.org>
CommitDate: Thu Jan 23 10:21:02 2020 -0500
Merge pull request #208 from agrare/bump_ansible_tower_client
Bump ansible_tower_client to v0.20.2
(cherry picked from commit 0b9e54c7730b723de374c6854bbe141b6a2f1758)
manageiq-providers-ansible_tower.gemspec | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Verified the issue in 126.96.36.199
The issue is that while using API v2, Tower refresh failed even though user credential was successfully validated. The Tower refresh failed with this message :
MIQ(ManageIQ::Providers::AnsibleTower::AutomationManager::Refresher#refresh) EMS: [Tower Automation Manager], id:  Unable to perform refresh for the following targets:
- undefined method `vault_password' for #<AnsibleTowerClient::Credential::Inputs:0x000055eea78a7578> Method:[block (2 levels) in <class:LogProxy>]"
This issue doesn't occur if there is a Vault credential on the Tower setup.
I verified the issue on a 188.8.131.52 appliance managing Tower 3.5.
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.