-
Bug
-
Resolution: Done
-
Undefined
-
Submariner 0.15.1
-
False
-
-
False
-
-
-
Submariner Sprint 2024-23, Submariner Sprint 2024-24, Submariner Sprint 2024-25, Submariner Sprint 2024-26, Submariner Sprint 2024-27, Submariner Sprint 2024-28, Submariner Sprint 2024-29, Submariner Sprint 2024-30, Submariner Sprint 2024-33, Submariner Sprint 2024-32, Submariner Sprint 2025-34
-
Important
-
No
Description of problem:
Version-Release number of selected component (if applicable):
ACM 2.8 Ga'ed
Submariner 0.15.1
How reproducible:
Steps to Reproduce:
1. When submariner is unhealthy due to issues with extra routes to establish healthier connectivity between managed clusters, submariner status on ACM UI doesn't report it.
Actual results: When submariner is unhealthy due to issues with extra routes to establish healthier connectivity between managed clusters, submariner status on ACM UI doesn't validate it.
Expected results: Submariner status on ACM UI should have proper validations to ensure submariner routes are actually healthy.
Additional info:
This issue was discussed here- https://redhat-internal.slack.com/archives/C0134E73VH6/p1687982082291729
Requesting asuryana and sgaddam@redhat.com to add more details to the bug.
- links to
-
RHEA-2025:145352
RHEA: Submariner 0.20 - bug fix and enhancement update