Project

General

Profile

Actions

Bug #20018

closed

REX creates zombie ssh processes when ProxyCommand is used for a tunnel

Added by Adam Ruzicka over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1461088

Description of problem:
Having local ssh configuration for ProxyCommand that contains "nc" like:

  1. cat /usr/share/foreman-proxy/.ssh/config
    Host proxyserver
    ProxyCommand

Host *
ProxyCommand ssh -q -i /usr/share/foreman-proxy/.ssh/id_rsa_foreman_proxy proxyrex@proxyserver nc %h %p #

then invoking and REX job leaves one ssh zombie proces.

smart_proxy_dynflow_core service must be restarted to clean the ssh defunct processes

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

How reproducible:
100%

Steps to Reproduce:
1. Have above-like ssh config
2. Run a REX job - it can fail or succeed, it doesnt matter. Even it can fail due to wrongly set .ssh/config, that does not matter either.
3. Check ssh processes on the Satellite/Capsule that invoked the ssh commands

Actual results:
  1. ps aux | grep defunct
    foreman+ 24776 0.0 0.0 0 0 ? Z 13:06 0:00 [ssh] <defunct>
    foreman+ 24848 0.0 0.0 0 0 ? Z 13:07 0:00 [ssh] <defunct>
    root 24856 0.0 0.0 112652 964 pts/0 S+ 13:07 0:00 grep --color=auto defunct #

(each REX job adds one such defunct process)

Expected results:
  1. ps aux | grep defunct
    root 24856 0.0 0.0 112652 964 pts/0 S+ 13:07 0:00 grep --color=auto defunct #

Additional info:


Related issues 1 (1 open0 closed)

Copied to Foreman Remote Execution - Bug #20129: REX creates zombie ssh processes when ProxyCommand is used for a tunnelReady For TestingAdam Ruzicka06/14/2017Actions
Actions

Also available in: Atom PDF