Bug 1584769

Summary:	Can't use RHV Credentials in Ansible Tower when using SSH connection instead of localhost
Product:	[oVirt] ovirt-ansible-collection	Reporter:	Petr Kubica <pkubica>
Component:	General	Assignee:	Martin Necas <mnecas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.1.4	CC:	mperina, omachace, tzumainn
Target Milestone:	ovirt-4.2.7	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-02 14:30:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Kubica 2018-05-31 15:24:41 UTC

Description of problem:
RHV Credentials are passed only when using localhost connection within Tower but it should also work when using SSH connection to engine (or other machine with SDK)

Version-Release number of selected component (if applicable):
oVirt.ovirt-ansible-roles (1.1.4)
oVirt.cluster-upgrade (1.1.7)
...

How reproducible:
always

Steps to Reproduce:
1. Have inventory with engine
3. Run project with any oVirt ansible role

Actual results:
Fails on missing credentials and url

Expected results:
Should work

Comment 1 Tzu-Mainn Chen 2018-06-08 14:14:12 UTC

This may be a generic issue; it appears to happen with OpenStack credentials as well.

Comment 2 Petr Kubica 2018-08-27 11:29:14 UTC

Verified
ovirt-ansible-image-template-1.1.8-0.1.master.20180821175704.el7.noarch
ovirt-ansible-roles-1.1.5-0.1.master.20180504182539.el7.centos.noarch
ovirt-ansible-cluster-upgrade-1.1.8-0.1.master.20180822173545.el7.noarch
ovirt-ansible-vm-infra-1.1.10-0.1.master.20180821100010.el7.noarch
ovirt-ansible-manageiq-1.1.12-0.1.master.20180823081650.el7.noarch

Comment 3 Raz Tamir 2018-09-05 08:54:33 UTC

QE verification bot: the bug was verified upstream

Comment 4 Sandro Bonazzola 2018-11-02 14:30:33 UTC

This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.