Description of problem (please be detailed as possible and provide log snippests): consumer is not able to communicate to the provider cluster with the error `failed to dial: context deadline exceeded` 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? 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? yes Can this issue reproduce from the UI? NA If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. create a provider and consumer cluster 2. storage cluster CR (consumer) will complain `failed to dial: context deadline exceeded` 3. Actual results: failed to dial: context deadline exceeded Expected results: Should be able to make a connection. Additional info:
Do we have an RCA?
On going thorugh the provider/consumer mode connectivity issue, i was able to establish the connectivity after reverting the changes introduced to have TLS for API server. https://github.com/red-hat-storage/ocs-operator/pull/1481. I assume some kind of changes required for the Client to use the certificates for establishing the connection . With the introduction of TLS, even the unsecure mode of connection was not possible
Is this now fixed by Bug 2055696? If so, can we close duplicate
Its now fixed by https://bugzilla.redhat.com/show_bug.cgi?id=2055699 *** This bug has been marked as a duplicate of bug 2055699 ***