-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.13, 4.12, 4.14, 4.15, 4.16, 4.17, 4.18
-
Moderate
-
None
-
Rejected
-
False
-
Description of problem:
Since OCPBUGS-14966 has been resolved, new DNS record propagation time has be lowered to 1-2 minutes total. Prior to this fix, we put in workarounds (https://github.com/openshift/cluster-ingress-operator/pull/944 and https://github.com/openshift/cluster-ingress-operator/pull/1127) that used the Load Balancer Hostname in conjunction with the Host HTTP header to create a more reliable test.
We should revert these workarounds in TestAWSELBConnectionIdleTimeout, TestAWSEIPAllocationsForNLB, and TestAWSLBSubnets as they reduce E2E coverage by not fully testing the DNS Record in the E2E connectivity tests.
Version-Release number of selected component (if applicable):
4.12+
How reproducible:
N/A
Steps to Reproduce:
1.Examine code in https://github.com/openshift/cluster-ingress-operator/pull/944 https://github.com/openshift/cluster-ingress-operator/pull/1127
Actual results:
Not using wildcard DNS record
Expected results:
Should use wildcard DNS record
Additional info:
https://github.com/openshift/cluster-ingress-operator/pull/944 was backported to 4.12 while https://github.com/openshift/cluster-ingress-operator/pull/1127 was only backported to 4.17. If it makes more sense to split this bug for each PR workaround, we can do that.
- is caused by
-
-
- Verified
-
-
-
- Closed
-
- relates to
-
-
- Closed
-