Bug 1731158

Summary:	[RFE] multisite playbook to verify connectivity amongst two sites
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	John Harrigan <jharriga>
Component:	Ceph-Ansible	Assignee:	Ali Maredia <amaredia>
Status:	CLOSED ERRATA	QA Contact:	Vasishta <vashastr>
Severity:	low	Docs Contact:	Ranjini M N <rmandyam>
Priority:	low
Version:	4.0	CC:	amaredia, asakthiv, aschoen, assingh, cbodley, ceph-eng-bugs, gabrioux, gmeno, kdreyer, nthomas, rmandyam, tserlin, vereddy, vumrao
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	4.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-ansible-4.0.38-1.el8cp, ceph-ansible-4.0.38-1.el7cp	Doc Type:	Enhancement
Doc Text:	.`ceph-ansible` performs additional connectivity check between two sites With this update, `ceph-ansible` performs additional connectivity checks between two sites prior to a realm pull.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-12 14:55:53 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:	1727980, 1890121

Description John Harrigan 2019-07-18 13:17:55 UTC

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):
ceph-ansible.noarch      3.2.15-1.el7cp


How reproducible:
Always


Steps to Reproduce:


Actual results:


Expected results:


Additional info:

Comment 2 Giridhar Ramaraju 2019-08-05 13:10:34 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 3 Giridhar Ramaraju 2019-08-05 13:11:36 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 6 Ali Maredia 2019-08-21 16:17:38 UTC

Casey,

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?

Comment 16 Ali Maredia 2020-09-17 04:43:02 UTC

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.

Comment 26 errata-xmlrpc 2021-01-12 14:55:53 UTC

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.

https://access.redhat.com/errata/RHSA-2021:0081