The `TestNetworkLoadBalancer` test in the ingress-operator's e2e tests is consistently failing as a result of the following error: "type":"LoadBalancerReady","status":"False","lastTransitionTime":"2020-12-17T13:34:07Z","reason":"SyncLoadBalancerFailed","message":"The service-controller component is reporting SyncLoadBalancerFailed events like: Error syncing load balancer: failed to ensure load balancer: error creating load balancer target group: \"ValidationError: Health check interval '5' not supported for target groups with the TCP protocol. Must be one of the following values '[10, 30]'" Pulled from https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-ingress-operator/511/pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-operator/1339551761060335616. More failures available here: https://prow.ci.openshift.org/pr-history/?org=openshift&repo=cluster-ingress-operator&pr=512
Verified in "4.7.0-0.nightly-2020-12-18-031435" release which has the PR merge. It is noted that the error no more occurs with ingresscontrollers having the NLB configuration in place: ----- $ oc -n openshift-ingress-operator get ingresscontroller internalapps -o yaml spec: domain: internalapps.aiyengar-oc47-1908758.qe.devcluster.openshift.com endpointPublishingStrategy: loadBalancer: providerParameters: aws: type: NLB type: AWS scope: External type: LoadBalancerService $ oc get route oc NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD service-unsecure service-unsecure-test1.internalapps.aiyengar-oc47-1908758.qe.devcluster.openshift.com ... 1 more service-unsecure http None $ curl service-unsecure-test1.internalapps.aiyengar-oc47-1908758.qe.devcluster.openshift.com -I HTTP/1.1 200 OK Accept-Ranges: bytes Content-Length: 28 Content-Type: text/html; charset=utf-8 Last-Modified: Tue, 27 Feb 2018 02:43:29 GMT Server: Caddy Date: Fri, 18 Dec 2020 09:07:03 GMT Set-Cookie: e96c07fa08f2609cadf847f019750244=444143347c5a402b2f6cd7ba774d8b6e; path=/; HttpOnly Cache-control: private ------ In non-patched version the route goes unreachable.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633