Description of problem: rhc-admin-move leaves ssh keys loaded into ssh-agent. After moving a lot of apps we have seen the number get close to 3000 keys still loaded in memory on the ex-srvs. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Run `ps -aux | grep ssh-agent | wc -l` on a broker take note how many is running 2. Use rhc-admin-mode to move a gear from one node to another 3. Rerun `ps -aux | grep ssh-agent | wc -l` Actual results: Each time rhc-admin-move is ran it leaves the ssh key loaded into ssh-agent causing it to take up resources(2800 running is about 2GB of ram) Expected results: It should clear the key from ssh-agent after completion Additional info:
Verified this bug on devenv_1850, and PASS. # rhc-admin-move ..... <--snip--> Identity added: /var/www/stickshift/broker/config/keys/rsync_id_rsa (/var/www/stickshift/broker/config/keys/rsync_id_rsa) Warning: Permanently added '10.72.198.196' (RSA) to the list of known hosts. Agent pid 15950 unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 15950 killed; <--snip--> Before move: # ps -ef | grep ssh-agent root 15944 14947 0 03:33 pts/1 00:00:00 grep ssh-agent During move: # ps -ef | grep ssh-agent root 15947 15325 0 03:33 pts/0 00:00:00 sh -c eval `ssh-agent`; ssh-add /var/www/stickshift/broker/config/keys/rsync_id_rsa; ssh -o StrictHostKeyChecking=no -A root.198.196 "rsync -aA -e 'ssh -o StrictHostKeyChecking=no' /var/lib/stickshift/16cee095b10d44468b79d5c9d1a9613d/ root.81.169:/var/lib/stickshift/16cee095b10d44468b79d5c9d1a9613d/"; ssh-agent -k After move: # ps -ef | grep ssh-agent root 16001 14947 0 03:33 pts/1 00:00:00 grep ssh-agent