-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.20.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
Yes
-
None
-
Proposed
-
Installer Sprint 275
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
CORS implementation for Custom DNS (https://issues.redhat.com/browse/OCPSTRAT-2215) breaks Gateway API DNS management. Visible in regressed Sippy component readiness: Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn Platform:gcp Suite:unknown Topology:ha Upgrade:none openshift-tests.[sig-network-edge][OCPFeatureGate:GatewayAPIController][Feature:Router][apigroup:gateway.networking.k8s.io] Ensure HTTPRoute object is created [Suite:openshift/conformance/parallel]A new job is permafailing (4/4) : periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-custom-dnsfail [github.com/openshift/origin/test/extended/router/gatewayapicontroller.go:443]: Timed out waiting for gateway "gateway-dj49q" DNSRecord to become ready
Version-Release number of selected component (if applicable):
4.20.0
How reproducible:
Periodic CI test is permafailing
Steps to Reproduce:
1. Run test periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-custom-dns
2. Fails every time
3.
Actual results:
Custom DNS doesn't cover the gateway-service-dns controller
Expected results:
Custom DNS should cover the gateway-service-dns controller, since it is a GA feature of OCP 4.19
Additional info:
- relates to
-
-
- POST
-
- links to