-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.19.0, 4.20.0
-
Quality / Stability / Reliability
-
False
-
-
0
-
Moderate
-
None
-
None
-
Rejected
-
OAPE Sprint 272
-
1
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-55832. The following is the description of the original issue:
—
Description of problem:
Since hypershift/pull/6068 was merged, the RouteExternalCertificate tests have been failing.
It can be seen in this run which runs the tests against a hosted cluster created via KubeVirt. The management cluster is baremetal.
The same tests pass when run against a hosted cluster created in AWS.
Version-Release number of selected component (if applicable):
4.19
How reproducible:
Always
Steps to Reproduce:
1. Create a hosted cluster created via Kubevirt. The management cluster should be baremetal.
2. Run OpenShift conformance tests against the hosted cluster.
3.
Actual results:
[sig-network][OCPFeatureGate:RouteExternalCertificate][Feature:Router][apigroup:route.openshift.io] with valid setup the router should support external certificate and the route is updated to use same external certificate then also the route is reachable [Suite:openshift/conformance/parallel] expand_less 3m14s
{ fail [github.com/openshift/origin/test/extended/router/external_certificate.go:413]: Unexpected error:
<*fmt.wrapError | 0xc00681f480>:
failed to make successful HTTPS request after retries: context deadline exceeded
{
msg: "failed to make successful HTTPS request after retries: context deadline exceeded",
err: <context.deadlineExceededError>{},
}
occurred
Ginkgo exit error 1: exit with code 1}
Expected results:
Tests marked as OCPFeatureGate:RouteExternalCertificate pass
Additional info:
Discussed in this slack thread.
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to
-
RHBA-2025:9278
OpenShift Container Platform 4.19.1 bug fix update