Closed spadgett closed 8 years ago
I stepped through RoutesService.getRouteWarning
, and warnings comes back empty. Yet we still show the message on the overview.
Self-assigning since I have an environment to reproduce.
I see the problem. routeWarningsByService[serviceId]
has this content
{"hello-openshift-localhost-dev":[],"route-edge":[]}
But this is our ng-if condition
(routeWarningsByService[serviceId] | hashSize) > 0 && otherRoutes
No route shows up on the overview as well if there are multiple routes and none is custom, TLS, or admitted.
RoutesService.getPreferredDisplayRoute
also does not choose the TLS route when everything else equal.
I get a warning about routes on the overview page ...
... but no routes have a warning on the routes page.
@jwforres