test: Cluster frontend ingress remain available is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=Cluster+frontend+ingress+remain+available https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=4.5&maxMatches=5&maxBytes=20971520&groupBy=job&search=Cluster+frontend+ingress+remain+available Frontends were unreachable during disruption for at least 4s of 1h9m47s (0%): Aug 21 08:57:33.793 E ns/openshift-authentication route/oauth-openshift Route stopped responding to GET requests over new connections Aug 21 08:57:33.793 E ns/openshift-console route/console Route stopped responding to GET requests over new connections Aug 21 08:57:33.929 I ns/openshift-authentication route/oauth-openshift Route started responding to GET requests over new connections Aug 21 08:57:34.006 I ns/openshift-console route/console Route started responding to GET requests over new connections Aug 21 08:57:35.793 E ns/openshift-console route/console Route stopped responding to GET requests on reused connections Aug 21 08:57:35.948 I ns/openshift-console route/console Route started responding to GET requests on reused connections Aug 21 09:36:38.793 E ns/openshift-console route/console Route stopped responding to GET requests on reused connections Aug 21 09:36:38.982 I ns/openshift-console route/console Route started responding to GET requests on reused connections
Target set to 4.7 while investigation is either ongoing or not yet started. Will be considered for earlier release versions when diagnosed and resolved.
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
The plan is to address this with https://issues.redhat.com/browse/NE-348. We'll continue tracking this work in the upcoming sprint.
Closing as we will track the work in https://issues.redhat.com/browse/NE-348.