Description of problem (please be detailed as possible and provide log snippests): rook-ceph-rbd-mirror pods show debug 2021-05-18 07:14:48.756 7faba8d1c680 -1 asok(0x55d6a127e000) AdminSocketConfigObs::init: failed: AdminSocket::bind_and_listen: The UNIX domain socket path /var/run/ceph/client.rbd-mirror-peer.16.4cc34565-eff6-46f8-9805-91761cf219c9-openshift-storage.94380315121088.asok is too long! The maximum length on this system is 107 Version of all relevant components (if applicable): OCP version:- 4.8.0-0.nightly-2021-05-15-141455 OCS version:- ocs-operator.v4.8.0-394.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 Can this issue reproducible? yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Deploy 2 OCP cluster 2. Connect them with submariner 3. Deploy cephrbdmirror pods and check logs Actual results: Pods logs:- http://pastebin.test.redhat.com/964594 Expected results: Additional info:
The socket takes the following construct: "$run_dir/$name.$pid.$cluster.$cctid.asok", so the $cluster part is definitely the problem here. Rook forms the cluster name with the ceph fsid + the namespace when creating the bootstrap peer, it uses --site-name. We need to decide which part to chop off... I feel like both are relevant, at least the cluster fsid. Thoughts Madhu for the DR integration?
What do you mean by a standalone cluster?
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 OpenShift Container Storage 4.8.0 container images bug fix and enhancement 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:3003