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

metric for ingresswithoutclassname does not decrease when classless ingresses cease to exist

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.12
    • Networking / router
    • None
    • Low
    • No
    • 2
    • Sprint 249, Sprint 250, Sprint 251, Sprint 252, Sprint 254, NE Sprint 255, NE Sprint 256, NE Sprint 257, NE Sprint 259, NE Sprint 261, NE Sprint 262, NE Sprint 263
    • 12
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: The ingress-to-route controller did not reset the openshift_ingress_to_route_controller_ingress_without_class_name metric for deleted ingresses.

      Consequence: If an ingress that was triggering the "IngressWithoutClassName" alert in the console was deleted, the alert continued firing.

      Fix: The ingress-to-route controller resets the metric for an ingress to 0 when the ingress is deleted.

      Result: The "IngressWithoutClassName" no longer fires for deleted ingresses.
      Show
      Cause: The ingress-to-route controller did not reset the openshift_ingress_to_route_controller_ingress_without_class_name metric for deleted ingresses. Consequence: If an ingress that was triggering the "IngressWithoutClassName" alert in the console was deleted, the alert continued firing. Fix: The ingress-to-route controller resets the metric for an ingress to 0 when the ingress is deleted. Result: The "IngressWithoutClassName" no longer fires for deleted ingresses.
    • Bug Fix
    • In Progress
    • This is a legit bug in current versions. Customers have noticed it and care about it. Needs a priority re-evaluation. If truly minor then close it and end the false sense of hope that open bugs give.

      Description of problem:

      We have an OKD 4.12 cluster which has persistent and 
increasing ingresswithoutclassname alerts with no ingresses normally 
present in the cluster. I believe the ingresswithoutclassname being 
counted is created as part of the ACME validation process managed by the
 cert-manager operator with it's openshift route addon which are torn down once the ACME validation is complete.

      Version-Release number of selected component (if applicable):

       4.12.0-0.okd-2023-04-16-041331

      How reproducible:

      seems very consistent. went away during an update but came back shortly after and continues to increase.

      Steps to Reproduce:

      1. create ingress w/o classname
2. see counter increase
3. delete classless ingress
4. counter does not decrease.

      Additional info:

      https://github.com/openshift/cluster-ingress-operator/issues/912

              mmasters1@redhat.com Miciah Masters
              oit-nate.childers Nate Childers (Inactive)
              Shudi Li Shudi Li
              Votes:
              1 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 5 hours
                  5h