Bug 2112852

Summary:	Provider cannot deduce API server reachability of API server
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Dhruv Bindra <dbindra>
Component:	ocs-operator	Assignee:	Dhruv Bindra <dbindra>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jilju Joy <jijoy>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	kramdoss, mmuench, muagarwa, nberry, ocs-bugs, odf-bz-bot, sostapov
Target Milestone:	---
Target Release:	ODF 4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	2120314 2136765 (view as bug list)		Environment:
Last Closed:	2023-02-08 14:06:28 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:	2136765, 2120314

Description Dhruv Bindra 2022-08-01 10:14:36 UTC

Description of problem (please be detailed as possible and provide log
snippests):
There is no way for the provider cluster to know that a consumer is not able to connect to the provider API endpoint.

Version of all relevant components (if applicable):


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?
We can manually ping the provider nodes from consumer nodes to check the connection

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
Always

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Create Provider cluster
2. Create Consumer cluster
3. Change storageProviderEndpoint


Actual results:
No information about consumer not able to reach to provider

Expected results:
Update storageConsumer CR with the heartbeat timestamp in regular intervals

Additional info:

Comment 2 Mudit Agarwal 2022-10-11 12:18:34 UTC

Fixed in the latest 4.12 builds

Comment 5 Jilju Joy 2022-10-21 09:18:56 UTC

Marking this bug as verified because this fix didn't cause any regression in ODF 4.12. The bug #2136765 can be used for verification when ODF 4.12 is available in Managed Services for testing.