Bug 1562013 - Use custom system SSH configuration for engine internal Ansible executions
Summary: Use custom system SSH configuration for engine internal Ansible executions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.3
: ---
Assignee: Ondra Machacek
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-29 11:40 UTC by Ondra Machacek
Modified: 2018-12-05 15:43 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-10 06:26:55 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1656480 0 unspecified CLOSED ansible rex fails if /etc/ssh/ssh_config has ProxyCommand /usr/bin/sss_ssh_knownhostsproxy -p %p %h 2021-02-22 00:41:40 UTC
oVirt gerrit 89601 0 master MERGED core: Don't use system SSH conf for Ansible 2018-04-09 11:20:53 UTC
oVirt gerrit 89994 0 ovirt-engine-4.2 MERGED core: Don't use system SSH conf for Ansible 2018-04-09 12:16:31 UTC

Internal Links: 1656480

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.
Note You need to log in before you can comment on or make changes to this bug.