Jay, would you take a look at this? Relevent code is in client-go/tools/leaderelection/resourcelock
Call chain to when RecordEvent should be called:
-> LeaderElector.acquire() or LeaderElector.renew()
The Scheme we were using with the event recorder was not properly initialized with the required types. This was previously reported upstream as https://github.com/kubernetes-incubator/service-catalog/issues/1628 and is being fixed by https://github.com/kubernetes-incubator/service-catalog/pull/1981
The fix is in the upstream release v0.1.15. Should be picked up by origin next week.
Delivered today with https://github.com/openshift/openshift-ansible/pull/8205
only fixed in master, still needs to be ported to 3.9.
reviewed with Paul, we'll only fix this in 3.10, we don't expect this to be that big of an issue with serviceability to warrant fixing it in 3.9.
Note again this was fixed in 3.10 with https://github.com/openshift/openshift-ansible/pull/8205
Change status to "ON_QA" since the corresponding image is ready.
Service catalog version:
The event info as below after changed leader pods:
[root@shared58r5-master-etcd-2 ~]# oc describe cm service-catalog-controller-manager -n kube-service-catalog
Type Reason Age From Message
---- ------ ---- ---- -------
Normal LeaderElection 3h service-catalog-controller-manager controller-manager-qzrfj-external-service-catalog-controller became leader
Normal LeaderElection 3h service-catalog-controller-manager controller-manager-fcw54-external-service-catalog-controller became leader
Normal LeaderElection 2h service-catalog-controller-manager controller-manager-d8dm7-external-service-catalog-controller became leader
Normal LeaderElection 1m service-catalog-controller-manager controller-manager-85pqb-external-service-catalog-controller became leader
Normal LeaderElection 36s service-catalog-controller-manager controller-manager-m85x9-external-service-catalog-controller 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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.