[QUESTION] Exception occurred while acquiring lock 'LeaseLock: kafka - strimzi-cluster-operator

[OLAMIDE100]

Hi, I just encountered the error below while deploying a new Kafka cluster using helm chart, though before today it was working properly.....

io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: PATCH at: https://34.118.224.1:443/apis/coordination.k8s.io/v1/namespaces/kafka/leases/strimzi-cluster-operator. Message: Operation cannot be fulfilled on leases.coordination.k8s.io "strimzi-cluster-operator": the object has been modified; please apply your changes to the latest version and try again. Received status: Status(apiVersion=v1, code=409, details=StatusDetails(causes=[], group=coordination.k8s.io, kind=leases, name=strimzi-cluster-operator, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Operation cannot be fulfilled on leases.coordination.k8s.io "strimzi-cluster-operator": the object has been modified; please apply your changes to the latest version and try again, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Conflict, status=Failure, additionalProperties={}).
at io.fabric8.kubernetes.client.KubernetesClientException.copyAsCause(KubernetesClientException.java:238) ~[io.fabric8.kubernetes-client-api-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.waitForResult(OperationSupport.java:507) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.handleResponse(OperationSupport.java:524) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.handlePatch(OperationSupport.java:419) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.handlePatch(OperationSupport.java:397) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.BaseOperation.handlePatch(BaseOperation.java:764) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.HasMetadataOperation.lambda$patch$2(HasMetadataOperation.java:231) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.HasMetadataOperation.patch(HasMetadataOperation.java:236) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.HasMetadataOperation.patch(HasMetadataOperation.java:251) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.dsl.internal.HasMetadataOperation.patch(HasMetadataOperation.java:44) ~[io.fabric8.kubernetes-client-6.13.4.jar:?]
at io.fabric8.kubernetes.client.extension.ResourceAdapter.patch(ResourceAdapter.java:305) ~[io.fabric8.kubernetes-client-api-6.13.4.jar:?]
at io.fabric8.kubernetes.client.extended.leaderelection.resourcelock.ResourceLock.update(ResourceLock.java:64) ~[io.fabric8.kubernetes-client-api-6.13.4.jar:?]
at io.fabric8.kubernetes.client.extended.leaderelection.LeaderElector.tryAcquireOrRenew(LeaderElector.java:247) ~[io.fabric8.kubernetes-client-api-6.13.4.jar:?]
at io.fabric8.kubernetes.client.extended.leaderelection.LeaderElector.lambda$renewWithTimeout$6(LeaderElector.java:207) ~[io.fabric8.kubernetes-client-api-6.13.4.jar:?]
at io.fabric8.kubernetes.client.extended.leaderelection.LeaderElector.lambda$loop$8(LeaderElector.java:292) ~[io.fabric8.kubernetes-client-api-6.13.4.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:840) ~[?:?]

[scholzj]

Kubernetes does not have any transaction or lock mechanism on its APIs. So typically, these 409 errors mean that someone else changed this resource while this operator instance tried to update it. In this case with the Lease Lock, it might be that other operator instance tool the Lease Lock few milliseconds before this one. So if it happens only once in a while, it can be considered normal and ignored. If it would be happening regularly and very often, it might indicate some issues which would need to be figured out, but that would need more information about your environment, setup, full logs of all operators etc.