| Summary: | gnome-keyring ssh-agent support appears to be unstable when used with ansible at high levels of parallelism | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dave McNeill <dave.mcneill> |
| Component: | gnome-keyring | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | debarshir, mclasen, stefw, walters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-25 16:24:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
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. |
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: