KCP does not reconcileEtcdMembers for deleted machines (release-0.3 branch) #3860
Labels
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
Milestone
What steps did you take and what happened:
failed to pass etcd health check: there are 2 healthy etcd pods, but 3 etcd members
What did you expect to happen:
KCP to re-create the 3rd CP machine
Anything else you would like to add:
Most probably this is a regression introduced by #3806 and more specifically by the nested if introduced in this change
https://github.com/kubernetes-sigs/cluster-api/blob/release-0.3/controlplane/kubeadm/controllers/controller.go#L502-L516
After a machine is deleted, EtcdIsHealthy returns an error due to
cluster-api/controlplane/kubeadm/internal/workload_cluster_etcd.go
Lines 129 to 131 in 7ed9b74
as a consequence we are entering in
cluster-api/controlplane/kubeadm/controllers/controller.go
Line 503 in 7ed9b74
ReconcileEtcdMembers
Environment:
/kind bug
The text was updated successfully, but these errors were encountered: