Description of problem: As reported in [0], after creating and exporting 200+ shares, the ceph-nfs-pacemaker container crashes and cannot be restarted. After analyzing the issue with the Manila squad and NFS Ganesha team, we found out this has to do with the fact that each exported share will spun 15~ threads consistently. By default, containers have a limit of 4096 pids. After creating a certain amount of shares and exporting them, we reach that limit easily. In order to fix it, we can either bump PidsLimit to a higher value, or set it to 0 so we don't constrain the ceph-nfs-pacemaker container to a certain limit. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1987235 How reproducible: Always reproducible Steps to Reproduce: 1. Deploy an environment with Manila with CephFS NFS 2. Create shares (manila create, approximately, 200 shares) 3. Export those shares (manila allow-access) 4. See the container crash Actual results: ceph-nfs-pacemaker container crashes, preventing the user to continue creating shares and accessing to the shares they already created Expected results: user should be able to create a higher amount of shares and have those available
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 (Red Hat Ceph Storage 4.2 Bug Fix update), 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-2021:3670
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days