-
Bug
-
Resolution: Done
-
Major
-
OSSM 2.1.1
-
None
-
False
-
None
-
False
-
Sprint 51, Sprint 52, Sprint 53, Sprint 54
OSSM Federation failover TLS error when setting importAsLocal : ‘true’ in two separate federated meshes
This issue is related to OSSM 2.1.1 federation failover case. The initial reporter
pantianying described the issue in community Istio Slack openshift channel
There is a OSSMDOC Jira mentioned this issue
https://issues.redhat.com/browse/OSSMDOC-395
Issue description:
pantianying tianying pan added a comment - 2022/02/07 8:33 AM
when set importAsLocal : 'true' in two separate federated mesh clusters , an application invokes service A, the TLS configuration is that of the Peer mesh. This will cause an error when the load balancer calls the in the service A which pod is in local mesh cluster:
envoy connection [C289] TLS error: 337047686:SSL routines:tls_process_server_certificate:certificate verify failed
How to reproduce :
...
OpenShift Version:
...
- blocks
-
OSSM-2617 OSSM Federation failover Doc Update Example yaml contents
- Closed
- is caused by
-
OSSM-1533 OSSM Federation Service importAsLocal failed to import same name service in failover case
- Closed
- is documented by
-
OSSM-2649 Release Notes, Known Issues and Bug Fixes for OSSM 2.2
- Closed
-
OSSM-2894 Service Mesh zstream 2.1.3/2.0.10/1.1.19 Release Notes
- Closed
- is related to
-
OSSM-2953 Federation Config - importAsLocal = true (HA/FO, etc)
- Closed
- links to
- mentioned on