Bug 1461158

Summary:	Frequent "unable to confirm openshift-controller-manager lease exists" errors during cluster horizontal runs
Product:	OpenShift Container Platform	Reporter:	Mike Fiedler <mifiedle>
Component:	Node	Assignee:	Clayton Coleman <ccoleman>
Status:	CLOSED ERRATA	QA Contact:	Mike Fiedler <mifiedle>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	aos-bugs, decarr, jokerman, mmccomas, mnewby, smunilla, trankin
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	aos-scalability-36
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-10 05:28:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Fiedler 2017-06-13 16:54:40 UTC

Description of problem:

Cluster is HA:  3 master/etcd, 2 infra, 305 compute nodes

Workload is create 1K projects with 6K pods (4K running) + secrets, services, builds, image streams, etc.   Full project spec is here:  https://github.com/mffiedler/svt/blob/master/openshift_scalability/config/pyconfigMasterVirtScalePause.yaml


During project creation/scale up the following message 

 atomic-openshift-master-controllers: E0613 11:45:05.948563   68412 leaderelection.go:136] unable to confirm openshift-controller-manager lease exists: endpoints "openshift-controller-manager" not found

popped 14,720 times - more or less evenly spread across the masters.


Version-Release number of selected component (if applicable): 3.6.105


Additional info: 

I'll add full master log location information in a comment.

Comment 3 Maru Newby 2017-06-15 00:17:03 UTC

The logging is unnecessary and does not represent an error condition.  The linked GH issue stops logging this normal condition.

Comment 4 Maru Newby 2017-06-15 19:01:26 UTC

PR has merged.

Comment 6 Mike Fiedler 2017-07-05 14:43:36 UTC

Verified on 3.6.132

Comment 8 errata-xmlrpc 2017-08-10 05:28:09 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/RHEA-2017:1716