release-openshift-ocp-installer-e2e-aws-upi-4.10 is regularly failing `[sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2 [Suite:openshift/conformance/parallel] [Suite:k8s]` Failure looks like: fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Sep 15 09:08:10.816: iperf2 MB/s received below baseline of 90 for client ip-10-0-74-86.ec2.internal to server ip-10-0-87-114.ec2.internal: 80 Is aws-upi somehow using slower instances than other aws jobs? See: https://sippy.ci.openshift.org/sippy-ng/jobs/4.10/analysis?filters=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22name%22%2C%22operatorValue%22%3A%22equals%22%2C%22value%22%3A%22release-openshift-ocp-installer-e2e-aws-upi-4.10%22%7D%5D%2C%22linkOperator%22%3A%22and%22%7D&tests=%5Bsig-network%5D%20Networking%20IPerf2%20%5BFeature%3ANetworking-Performance%5D%20should%20run%20iperf2%20%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5D%20%5BSuite%3Ak8s%5D Example failing job: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-upi-4.10/1438054970514477056
The AWS old-rhcos job for 4.10 is failing with these too
*** This bug has been marked as a duplicate of bug 2000754 ***