-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.14
This is a clone of issue OCPBUGS-55338. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-29354. The following is the description of the original issue:
—
Description of problem:
ingress-to-route controller does not provide any information about failed conversions from ingress to route. This is a big issue in environments heavily dependent on the ingress objects. The only way to find why a route is not created is guess and try as the only information one can get is that the route is not created.
Version-Release number of selected component (if applicable):
OCP 4.14
How reproducible:
100%
Steps to Reproduce:
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: route.openshift.io/termination: passthrough name: hello-openshift-class namespace: test spec: ingressClassName: openshift-default rules: - host: ingress01-rhodain-test01.apps.rhodain03.sbr-virt.gsslab.brq2.redhat.com http: paths: - backend: service: name: myapp02 port: number: 8080 path: / pathType: Prefix tls: - {}
Actual results:
Route is not created and no error is logged
Expected results:
En error is provided in the events or at least in the controllers logs. The events are prefered as the ingress objects are mainly created by uses without cluster admin privileges.
Additional info:
- blocks
-
OCPBUGS-56152 Provide error report from ingress-to-route controller
-
- Closed
-
- clones
-
OCPBUGS-55338 Provide error report from ingress-to-route controller
-
- Closed
-
- is blocked by
-
OCPBUGS-55338 Provide error report from ingress-to-route controller
-
- Closed
-
- is cloned by
-
OCPBUGS-56152 Provide error report from ingress-to-route controller
-
- Closed
-
- links to
-
RHBA-2025:7669 OpenShift Container Platform 4.17.z bug fix update