-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
None
On 4.13 cluster, when user just updating app ingress visibility, it shows error like
Can't update route selectors to default ingress 'xxxx' in cluster 'xxxxxx'. For more information on how to be supported...
Expected result:
There shouldn't be related error about route selectors once customer didn't update it.
The root cause is that UI generated the unchanged part into the request body. Backend will return error message accordingly.
UI shouldn't generate the non-changing area into request body.
User can just update ingress visibility (Make router private)
- depends on
-
HAC-3994 4.13: UI work for OSD/ROSA managed Ingress improvements
- Closed
-
HAC-5128 4.14: UI work for OSD/ROSA managed Ingress improvements
- Closed
- is related to
-
HAC-3994 4.13: UI work for OSD/ROSA managed Ingress improvements
- Closed
-
HAC-5128 4.14: UI work for OSD/ROSA managed Ingress improvements
- Closed
- mentioned on