Bug 1717011
| Summary: | Playbook is taking long time at TASK - ceph-defaults : check if the ceph mon socket is in-use | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Manjunatha <mmanjuna> |
| Component: | Ceph-Ansible | Assignee: | Dimitri Savineau <dsavinea> |
| Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
| Severity: | medium | Docs Contact: | Erin Donnelly <edonnell> |
| Priority: | medium | ||
| Version: | 3.2 | CC: | aschoen, assingh, ceph-eng-bugs, ceph-qe-bugs, dsavinea, edonnell, gabrioux, gmeno, nthomas, tchandra, tserlin |
| Target Milestone: | rc | ||
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-4.0.0-0.1.rc9.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.The Ansible playbook no longer takes hours to complete the `fuser` command
Previously, on a system running thousands of processes, the `fuser` command in the Ansible playbook could take several minutes or hours to complete because it iterates over all PID present in the `/proc` directory. Because of this, the handler tasks take a long time to complete checking if a Ceph process is already running. With this update, instead of using the `fuser` command, the Ansible playbook now checks the socket file in the `/proc/net/unix` directory, and the handler tasks that check the Ceph socket completes almost instantly.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-31 12:46:18 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: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1730176 | ||
|
Comment 7
Giridhar Ramaraju
2019-08-05 13:10:53 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0312 |