Description of problem: SRO was not adjusted to SNO API behavior - aka, it's leader election lease is 15s (which will cause it to be restarted in case of api rollout on SNO). Version-Release number of selected component (if applicable): 4.9 How reproducible: Every time Steps to Reproduce: 1. Deploy SRO in SNO 2. 3. Actual results: SRO restarts when deployed on SNO which can cause OOT driver container loading and ordering issues. Expected results: SRO handles longer timeout to support SNO API availability. Additional info:
verified Result: [ocpadmin@ec2-18-217-45-133 sro]$ oc get lease b6ae617b.openshift.io -n openshift-special-resource-operator -o json { "apiVersion": "coordination.k8s.io/v1", "kind": "Lease", "metadata": { "creationTimestamp": "2021-11-19T08:28:02Z", "name": "b6ae617b.openshift.io", "namespace": "openshift-special-resource-operator", "resourceVersion": "43695", "uid": "23754f7e-c577-4ab4-b07a-c137191f62ab" }, "spec": { "acquireTime": "2021-11-19T08:28:02.000000Z", "holderIdentity": "special-resource-controller-manager-678bc496f4-7w88p_679f780b-e622-4d6a-95aa-e136eb53e651", "leaseDurationSeconds": 137, "leaseTransitions": 0, "renewTime": "2021-11-19T08:33:15.859851Z" } } [ocpadmin@ec2-18-217-45-133 sro]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2021-11-15-034648 True False 75m Cluster version is 4.10.0-0.nightly-2021-11-15-034648 [ocpadmin@ec2-18-217-45-133 sro]$ oc logs special-resource-controller-manager-678bc496f4-jvfbx -n openshift-special-resource-operator -c manager I1119 07:39:56.463775 1 request.go:665] Waited for 1.038346464s due to client-side throttling, not priority and fairness, request: GET:https://172.30.0.1:443/apis/network.openshift.io/v1?timeout=32s 2021-11-19T07:39:57.717Z INFO controller-runtime.metrics metrics server is starting to listen {"addr": "127.0.0.1:8080"} 2021-11-19T07:39:57.729Z INFO setup starting manager I1119 07:39:57.729775 1 leaderelection.go:248] attempting to acquire leader lease openshift-special-resource-operator/b6ae617b.openshift.io... 2021-11-19T07:39:57.730Z INFO starting metrics server {"path": "/metrics"} I1119 07:39:57.751592 1 leaderelection.go:258] successfully acquired lease openshift-special-resource-operator/b6ae617b.openshift.io 2021-11-19T07:39:57.751Z DEBUG events Normal {"object": {"kind":"ConfigMap","namespace":"openshift-special-resource-operator","name":"b6ae617b.openshift.io","uid":"6fd43ddb-bbf8-49a8-a6f3-c0bb4c527cee","apiVersion":"v1","resourceVersion":"24524"}, "reason": "LeaderElection", "message": "special-resource-controller-manager-678bc496f4-jvfbx_972718d9-17ab-45d8-8d7c-f9d3efb9fa2d became leader"} 2021-11-19T07:39:57.751Z DEBUG events Normal {"object": {"kind":"Lease","namespace":"openshift-special-resource-operator","name":"b6ae617b.openshift.io","uid":"d9e1769d-9773-4edb-b1b9-26e4fda799dc","apiVersion":"coordination.k8s.io/v1","resourceVersion":"24525"}, "reason": "LeaderElection", "message": "special-resource-controller-manager-678bc496f4-jvfbx_972718d9-17ab-45d8-8d7c-f9d3efb9fa2d became leader"}
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 (Moderate: OpenShift Container Platform 4.10.3 security 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. https://access.redhat.com/errata/RHSA-2022:0056