Bug 1374259

Summary: [install using ansible openshift-playbook] Too many open files
Product: OpenShift Container Platform Reporter: Miheer Salunke <misalunk>
Component: InstallerAssignee: Andrew Butcher <abutcher>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: high    
Version: 3.1.0CC: abutcher, aos-bugs, erich, erjones, hgraham, jeder, jokerman, mmccomas
Target Milestone: ---Keywords: Performance
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-08 20:17:36 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:

Description Miheer Salunke 2016-09-08 11:07:54 UTC
Description of problem:

We face a problem during OSEv3.2.1.13 installation using ansible openshift-playbooks : 
    "Too many open files" error

Find enclosed :
- ansible host inventory file
- ansible -vvvv output file
- ulimit from user launching ansible-playbook

We never faced this problem during previous installations on POC environment.


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

How reproducible:
Always on customer side

Steps to Reproduce:
1. After running ansible playbook with the attached inventory file
2.
3.

Actual results:
Installation fails with  Too many open files error

Expected results:
Installation succeeds.

Additional info:

Comment 2 Jason DeTiberus 2016-09-08 14:31:59 UTC
What version of ansible is being used and what does /etc/ansible/ansible.cfg look like?

Comment 11 Andrew Butcher 2016-09-12 20:12:14 UTC
*** Bug 1359849 has been marked as a duplicate of this bug. ***

Comment 19 Scott Dodson 2017-06-08 20:17:36 UTC
Without a consistent reproducer we're not likely to resolve this. Also, we have resolved an issue where ansible was run via batch processes, like via `nohup` that leaked file descriptors.

See https://bugzilla.redhat.com/show_bug.cgi?id=1439277 for details of that.