-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.13
-
None
-
No
-
False
-
Description of problem:
When installing SNO with bootstrap in place the cluster-policy-controller hangs for 6 minutes waiting for the lease to be acquired.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1.Run the PoC using the makefile here https://github.com/eranco74/bootstrap-in-place-poc 2.Observe the cluster-policy-controller logs post reboot
Actual results:
I0530 16:01:18.011988 1 leaderelection.go:352] lock is held by leaderelection.k8s.io/unknown and has not yet expired I0530 16:01:18.012002 1 leaderelection.go:253] failed to acquire lease kube-system/cluster-policy-controller-lock I0530 16:07:31.176649 1 leaderelection.go:258] successfully acquired lease kube-system/cluster-policy-controller-lock
Expected results:
Expected the bootstrap cluster-policy-controller to release the lease so that the cluster-policy-controller running post reboot won't have to wait the lease to expire.
Additional info:
Suggested resolution for bootstrap in place: https://github.com/openshift/installer/pull/7219/files#diff-f12fbadd10845e6dab2999e8a3828ba57176db10240695c62d8d177a077c7161R44-R59
- blocks
-
OCPBUGS-14867 When installing SNO with bootstrap in place it takes cluster-policy-controller 6 minutes to acquire the leader lease
- Closed
- duplicates
-
OCPBUGS-7390 During SNO installation pods failed to get created due to missing openshift.io/sa.scc.uid-range annotation
- Closed
- is cloned by
-
OCPBUGS-14661 [4.12] When installing SNO with bootstrap in place it takes cluster-policy-controller 6 minutes to acquire the leader lease
- Closed
-
OCPBUGS-14867 When installing SNO with bootstrap in place it takes cluster-policy-controller 6 minutes to acquire the leader lease
- Closed
-
OCPBUGS-14868 When installing SNO with bootstrap in place it takes cluster-policy-controller 6 minutes to acquire the leader lease
- Closed
- links to
-
RHEA-2023:5006 rpm