-
Bug
-
Resolution: Done
-
Minor
-
None
-
4.13
-
None
-
Informational
-
None
-
Sprint 231, Sprint 232
-
2
-
Rejected
-
False
-
-
-
Bug Fix
-
Done
Description of problem:
The cluster-ingress-operator's udpateIngressClass function logs "updated IngressClass" on a failure, when it should be logging that on a success.
Version-Release number of selected component (if applicable):
4.8+
How reproducible:
Easily
Steps to Reproduce:
# Simulate a change in an ingressclass that will be reconciled oc apply -f - <<EOF apiVersion: networking.k8s.io/v1 kind: IngressClass metadata: name: openshift-default spec: controller: openshift.io/ingress-to-route parameters: apiGroup: operator.openshift.io kind: IngressController name: default scope: Namespace namespace: "test" EOF # Look at logs oc logs -n openshift-ingress-operator $(oc get -n openshift-ingress-operator pods --no-headers | head -1 | awk '{print $1}') -c ingress-operator | grep "updated IngressClass" #No output
Actual results:
<none>
Expected results:
2023-01-26T20:37:19.210Z INFO operator.ingressclass_controller ingressclass/ingressclass.go:63 updated IngressClass ...
Additional info:
- blocks
-
OCPBUGS-6701 The ingress-operator spuriously updates ingressClass on startup
- Closed
- links to