Bug 1311605 - gnome-keyring ssh-agent support appears to be unstable when used with ansible at high levels of parallelism
Summary: gnome-keyring ssh-agent support appears to be unstable when used with ansible...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 23
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-24 15:12 UTC by Dave McNeill
Modified: 2016-02-25 16:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-25 16:24:57 UTC
Type: Bug


Attachments (Terms of Use)

Description Dave McNeill 2016-02-24 15:12:26 UTC
Description of problem:

I have a population of over 1000 VMs which I manage using ansible. When I run ansible over the entire set with increased parallelism, after a time, the ssh-agent appears to have failed.

If I load the the my into the standard openssh agent and use that, the run is fine.

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

gnome-keyring-3.18.3-1.fc23.x86_64

How reproducible:

Every time

Steps to Reproduce:
1. have an inventory of 1000+ vms
2. add ssh key to gnome-keyring agent
3. ansible all -o -f 50 -m ping

Actual results:

Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': Enter passphrase for key '/home/davem/.ssh/id_dsa': 

Expected results:

host1.example.com | SUCCESS => {"changed": false, "ping": "pong"}
host2.example.com | SUCCESS => {"changed": false, "ping": "pong"}
host3.example.com | SUCCESS => {"changed": false, "ping": "pong"}
host4.example.com | SUCCESS => {"changed": false, "ping": "pong"}
(etc, etc)

Additional info:

Comment 1 Dave McNeill 2016-02-25 16:24:57 UTC
Turns out the gnome-settings-daemon was failing when it runs out of file descriptors. I've increased ulimit -n and it's fine now.


Note You need to log in before you can comment on or make changes to this bug.