Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-29354

Provide error report from ingress-to-route controller

XMLWordPrintable

    • No
    • NE Sprint 257, NE Sprint 258, NE Sprint 259, NE Sprint 260, NE Sprint 261, NE Sprint 262, NE Sprint 263, NE Sprint 264
    • 8
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      *Cause*: Lack of error event
      *Consequence*: No error events when failed conversion from Ingress to Route
      *Fix*: Error Event implemented to emit when failed conversion
      *Result*: Bug doesn’t present anymore.
      Show
      *Cause*: Lack of error event *Consequence*: No error events when failed conversion from Ingress to Route *Fix*: Error Event implemented to emit when failed conversion *Result*: Bug doesn’t present anymore.
    • Bug Fix
    • In Progress

      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:

          

       

              rh-ee-alsyed Ali Syed
              rhn-support-rhodain1 Roman Hodain
              Melvin Joseph Melvin Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: