This is a clone of issue OCPBUGS-37668. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-23795. The following is the description of the original issue:
—
Description of problem:
After a controlled restart of the sriov operator (ex. rollout during an upgrade) it is taking 5+ mins to acquire the lease on startup. I1123 13:20:44.792821 1 leaderelection.go:245] attempting to acquire leader lease openshift-sriov-network-operator/a56def2a.openshift.io... I1123 13:25:56.033843 1 leaderelection.go:255] successfully acquired lease openshift-sriov-network-operator/a56def2a.openshift.io This LeaderElectionReleaseOnCancel: true is missing from https://github.com/openshift/sriov-network-operator/blob/master/main.go#L104 The impact is slow recovery from any controlled restart of the sriov operator.
Version-Release number of selected component (if applicable):
4.14.0-202311060529
How reproducible:
100%
Steps to Reproduce:
1. Restart sriov operator
2.
3.
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-37668 [4.17] SNO: SRIOV Operator long lease acquisition after a controlled shutdown/restart
-
- POST
-
- is blocked by
-
-
- POST
-