-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.16.0
-
None
-
Low
-
No
-
Rejected
-
False
-
See below for details of the failure mode. Not the first time a new test has run into this – we should add the linter I wrote to detect this https://github.com/stbenjam/no-empty-http-proxy
Description of problem:
With DNS changes (potentially related to OCPBUGS-33018), the BuildConfig webhook tests consistently fail.
Version-Release number of selected component (if applicable):
4.16.0
How reproducible:
Always
Steps to Reproduce:
1. Run origin build test suite on metal-ipi clusters
Actual results:
Webhook test fails with:
{ fail [github.com/openshift/origin/test/extended/builds/webhook.go:35]: Failed posting webhook: Post "https://api.ostest.test.metalkube.org:6443/apis/build.openshift.io/v1/namespaces/e2e-test-build-webhooks-f98nn/buildconfigs/pushbuild/webhooks/secret200/generic": dial tcp: lookup api.ostest.test.metalkube.org on 172.30.0.10:53: no such host
Ginkgo exit error 1: exit with code 1}
Expected results:
Tests pass
Additional info:
Example failing test: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/28750/pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6/1787438954933391360
- relates to
-
-
- Closed
-
