Bug 1794047
| Summary: | Tower provider throws error when using v2 api endpoint | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
| Component: | Providers | Assignee: | Adam Grare <agrare> |
| Status: | CLOSED ERRATA | QA Contact: | Nandini Chandra <nachandr> |
| Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Priority: | medium | ||
| Version: | 5.11.0 | CC: | agrare, akarol, dmetzger, gocallag, greartes, guillaume.pavese, irshad.ahmed, jfrey, jhardy, mheppler, mparkins, ngupta, obarenbo, saali, simaishi |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.10.15 | Flags: | simaishi:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | testathon | ||
| Fixed In Version: | 5.10.15.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1740860 | Environment: | |
| Last Closed: | 2020-02-25 05:39:24 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: | |||
|
Comment 2
CFME Bot
2020-01-23 15:32:17 UTC
Verified the issue in 5.10.15.1 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: [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.10.15.1 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. https://access.redhat.com/errata/RHSA-2020:0589 |