Description of problem:
Using RHCS 3.2z2 and ceph-ansible to deploy multisite, experienced failures in
sync operations due to connectivity issues amongst the two sites.
It would be helpful if ceph-ansible performed a verification of connectivity
amongst the two sites, as a pre-check to deploying multisite:
* RGWs on site1 to site2 (bi-directional)
* MONs on site1 to site2 (bi-directional)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate.
Would a `realm pull` exit with status 1 if the verification of connectivity to the pull host fails?
Also can you explain why ceph-ansible should keep deploying if some of the endpoints aren't up/reachable?
I opened up this PR https://github.com/ceph/ceph-ansible/pull/5797 which is performing one of the checks in https://github.com/ceph/ceph-ansible/pull/4524. PR 4524 would be overly complicated for the instance where there is more than 1 RGW on a machine and checking to make sure the pull endpoint is reachable is the major check we need to verify connectivity anyway.
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 (Important: Red Hat Ceph Storage 4.2 Security and 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.