Closed gyfora closed 1 year ago
@gyfora did you want to submit a fix for this?
@shawkins I am afraid it may be difficult due to some internal legal/process reasons with my employer. But I will follow up on this to see how I can contribute fixes/patches in the future.
Describe the bug
The https://github.com/fabric8io/kubernetes-client/blob/master/kubernetes-client-api/src/main/java/io/fabric8/kubernetes/client/extended/leaderelection/LeaderElector.java#L164 module incorrectly always logs
Failed to acquire lease
. Even if it was successfulFabric8 Kubernetes Client version
6.6.2
Steps to reproduce
Start LeaderElector
Expected behavior
Only log failure if it failed
Runtime
Kubernetes (vanilla)
Kubernetes API Server version
1.25.3@latest
Environment
macOS
Fabric8 Kubernetes Client Logs
No response
Additional context
No response