-
Bug
-
Resolution: Done-Errata
-
Major
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
2
-
None
-
None
-
None
-
Rejected
-
OAPE Sprint 270
-
1
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
Failed CI job example: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/multi-pr-openshift-hypershift-6064-openshift-api-2268-e2e-aws-ovn-hypershift-conformance/1914602282180153344
Description of problem:
[sig-network][OCPFeatureGate:RouteExternalCertificate][Feature:Router][apigroup:route.openshift.io][Skipped:Disconnected] with valid setup the router should support external certificate and the route is updated to remove the external certificate then also the route is reachable and serves the default certificate [Suite:openshift/conformance/parallel] openshift/origin test case in the conformance suite fails when running on an HyperShift cluster
Version-Release number of selected component (if applicable):
4.19, affects only the HyperShift platform
How reproducible:
Run the [OCPFeatureGate:RouteExternalCertificate] test cases from origin on a HyperShift cluster
Steps to Reproduce:
Proof PR with test result: https://github.com/openshift/hypershift/pull/6064 > "multi-pr-openshift-hypershift-6064-openshift-api-2268-e2e-aws-ovn-hypershift-conformance" Job
Actual results:
The test should pass.
Expected results:
The test case expects the ingress certificate at the router pod to have to Issuer.CommonName: "ingress-operator" however since HyperShift does not issue certs the same way OpenShift SelfManagedHA does from the ingress-operator, the Issuer.CommonName is "root-ca".
Additional info:
Fixing the test case can help succeed the e2e on hypershift platform
- links to
-
RHEA-2024:11038
OpenShift Container Platform 4.19.z bug fix update