Bug 1998103

Summary: The removed ingresscontrollers should not be counted in ingress_controller_conditions metrics
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Andrey Lebedev <alebedev>
Networking sub component: router QA Contact: jechen <jechen>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aiyengar, aos-bugs, hongli, hongyli, jechen, mmasters
Version: 4.8   
Target Milestone: ---   
Target Release: 4.8.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-12 06:01:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1972977    
Bug Blocks:    

Comment 1 jechen 2021-08-26 15:59:20 UTC

Verified with pre-PR merge build built with cluster-bot: launch openshift/cluster-ingress-operator#649

$ oc get clusterversion
NAME      VERSION                                                  AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.ci.test-2021-08-26-133353-ci-ln-g1lmrlk-latest   True        False         70m     Cluster version is 4.8.0-0.ci.test-2021-08-26-133353-ci-ln-g1lmrlk-latest

# 1. cordon all worker nodes, so worker nodes were all schedulingDisabled

$ oc get node
NAME                                       STATUS   ROLES    AGE   VERSION
ci-ln-g1lmrlk-f76d1-57w8h-master-0         Ready    master   74m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-master-1         Ready    master   73m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-master-2         Ready    master   73m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-worker-a-57nn7   Ready    worker   66m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-worker-b-kl4fz   Ready    worker   66m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-worker-c-n8tbj   Ready    worker   66m   v1.21.1+9807387
$ oc adm cordon -l node-role.kubernetes.io/worker=
node/ci-ln-g1lmrlk-f76d1-57w8h-worker-a-57nn7 cordoned
node/ci-ln-g1lmrlk-f76d1-57w8h-worker-b-kl4fz cordoned
node/ci-ln-g1lmrlk-f76d1-57w8h-worker-c-n8tbj cordoned

$ oc get node
NAME                                       STATUS                     ROLES    AGE   VERSION
ci-ln-g1lmrlk-f76d1-57w8h-master-0         Ready                      master   85m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-master-1         Ready                      master   85m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-master-2         Ready                      master   85m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-worker-a-57nn7   Ready,SchedulingDisabled   worker   77m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-worker-b-kl4fz   Ready,SchedulingDisabled   worker   78m   v1.21.1+9807387
ci-ln-g1lmrlk-f76d1-57w8h-worker-c-n8tbj   Ready,SchedulingDisabled   worker   78m   v1.21.1+9807387

# 2. created a custom ingresscontroller  test-12345
oc create -f custom-ingresscontroller.yaml
ingresscontroller.operator.openshift.io/test-12345 created
$ cat custom-ingresscontroller.yaml 
kind: IngressController
apiVersion: operator.openshift.io/v1
  name: test-12345
  namespace: openshift-ingress-operator
    name: router-certs-default
  domain: test-12345.ci-ln-g1lmrlk-f76d1.origin-ci-int-gce.dev.openshift.com
  replicas: 1
    type: NodePortService

# 3. (waited some time) on console UI, from monitoring->alert, verified that "IngressControllerUnavailable" and "IngressControllerDegraded" alerts were presented

# 4. Deleted the custom ingresscontroller test-12345, waited a minute, verified that previous "IngressControllerUnavailable" and "IngressControllerDegraded" alerts were cleared.

Comment 7 errata-xmlrpc 2021-10-12 06:01:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.8.14 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.