Bug 1562013

Summary:	Use custom system SSH configuration for engine internal Ansible executions
Product:	[oVirt] ovirt-engine	Reporter:	Ondra Machacek <omachace>
Component:	Backend.Core	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.2	CC:	bugs, lsvaty, mperina
Target Milestone:	ovirt-4.2.3	Flags:	rule-engine: ovirt-4.2+ lsvaty: testing_ack+
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-05-10 06:26:55 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 Ondra Machacek 2018-03-29 11:40:42 UTC

Description of problem:
Use custome system SSH configuration for engine internal Ansible executions

Version-Release number of selected component (if applicable):
4.2.2

How reproducible:
always

Steps to Reproduce:
1. Run any action which exectues Ansible internaly from engine.
2. Check if system SSH configuration was used.

Actual results:
It is.

Expected results:
It isn't.

Additional info:

Comment 1 Martin Perina 2018-04-03 08:12:57 UTC

This reverts changes performed by fixes for BZ1529851, we will no longer care about system SSH configuration, so IPA users who added engine to IPA domain will no longer need to remove SSH configuration specific to IPA.

Comment 2 Petr Kubica 2018-04-20 18:41:37 UTC

Verified
INFO  [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [2beba297-c523-49c5-aca6-040e1e23b4ed] Executing Ansible command: ANSIBLE_STDOUT_CALLBACK=hostupgradeplugin [/usr/bin/ansible-playbook, --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config, --check, --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa, --inventory=/tmp/ansible-inventory4484092345708873471, /usr/share/ovirt-engine/playbooks/ovirt-host-upgrade.yml] [Logfile: null]

ovirt-engine-4.2.3.2-0.1.el7.noarch

Comment 3 Sandro Bonazzola 2018-05-10 06:26:55 UTC

This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 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.