-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
False
-
-
False
-
XCMSTRAT-589 - [Internal Preview] OCM console can connect to regional OCM instances to manage cluster lifecycle
-
-
-
ACM Console Sprint 265
Description of the Problem
User has opened a ready regionalized HCP cluster details and went to Networking tab.
Under "Application ingress" section, the "Default application router"value indicated as undefined. See inline screenshot.
It could be due to the issue with ingress endpoint that eventually return as 404 during backend request as seen in above screenshot
How reproducible:
Always
Steps to Reproduce:
- Open OCM UI staging
- Open a ready regionalized HCP cluster(installed in the region : ap-southeast-1)
- Go to Networking tab.
- See the "Default application router" value.
Actual results:
The default application router value shown as "*.undefined" and it is wrong.
Expected results:
The default application router value should show valid value not as "undefined" in the field.
- blocks
-
OCMUI-2524 Make the multiRegion version of cluster details the default version
- Review
- depends on
-
OCMUI-2839 Cannot delete a regional cluster
- Code Review