Currently, when you create a new ceph client we also create a CephContext to hold some global information. Each client that ganesha creates is currently creating its own CephContext and those can interfere with one another. Ensure that we only create a CephContext when one doesn't already exist.
I see that this was reassigned to cephfs. To be clear, this is _not_ a cephfs specific problem, as far as I can tell. The CephContext is also used by librados, and programs that use it directly will need to be fixed in a similar fashion.
I've been tracking this in the associated upstream ceph bug (# 21512). There is a pull request in flight now but it needs some review and an ack from one of the authors of that piece of code.
Upstream set has been merged.
Provided qa_ack, clearing needinfo flag.
Thanks for the Help Patrick Moving this bug to verified state.
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-2018:1259