Bug 1780843

Summary: KCM cannot recover from deleting its lease configmap
Product: OpenShift Container Platform Reporter: Mike Dame <mdame>
Component: kube-controller-managerAssignee: Mike Dame <mdame>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, deads, jokerman, maszulik, mdame, mfojtik, mmccomas, xxia, yinzhou
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Kube Controller Manager did not have permissions to recreate its lease configmap Consequence: KCM would fail to properly secure lease Fix: Updated KCM permissions created by OpenShift KCM Operator Result: KCM can now recover from lease configmap deletion
 Story Points: ---
Clone Of: 1744984 Environment:
Last Closed: 2020-01-23 11:18:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1744984    
Bug Blocks: 1718061, 1781240    

Comment 2 zhou ying 2019-12-12 03:02:59 UTC 
Confirmed with payload: 4.3.0-0.nightly-2019-12-11-204310, the issue has fixed:

[root@dhcp-140-138 ~]# oc get cm -n kube-system
NAME                                 DATA   AGE
bootstrap                            1      95m
cluster-config-v1                    1      104m
extension-apiserver-authentication   6      104m
kube-controller-manager              0      104m
root-ca                              1      104m
[root@dhcp-140-138 ~]# oc delete cm/kube-controller-manager  -n kube-system
configmap "kube-controller-manager" deleted
[root@dhcp-140-138 ~]# oc get cm -n kube-system
NAME                                 DATA   AGE
bootstrap                            1      96m
cluster-config-v1                    1      104m
extension-apiserver-authentication   6      104m
kube-controller-manager              0      2s
root-ca                              1      104m
Comment 4 errata-xmlrpc 2020-01-23 11:18:15 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, 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/RHBA-2020:0062