New commit detected on ManageIQ/manageiq-providers-ansible_tower/ivanchuk: https://github.com/ManageIQ/manageiq-providers-ansible_tower/commit/02568cbf63ae1a81768bbd0061c7da66ae8a1b08 commit 02568cbf63ae1a81768bbd0061c7da66ae8a1b08 Author: Jason Frey <jfrey> AuthorDate: Thu Jan 23 10:21:02 2020 -0500 Commit: Jason Frey <jfrey> 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) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1794046 manageiq-providers-ansible_tower.gemspec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Verified in 5.11.2.2
The issue is that Tower refresh failed even though credentials were successfully validated. The Tower refresh failed with this message : MIQ(ManageIQ::Providers::AnsibleTower::AutomationManager::Refresher#refresh) EMS: [Tower Automation Manager], id: [99000000000005] 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 5.11.2.2 appliance managing Tower 3.6