- Related issues: #2191 [BUG] Promote fail, cluster stays in Provisioning phase
Category:
- Host
Verification Steps
- Create a 4-node Harvester cluster.
- Wait for three nodes to become control plane nodes (role is control-plane,etcd,master).
- Delete one of the control plane nodes.
- The remaining worker node should be promoted to a control plane node (role is control-plane,etcd,master).
Expected Results
-
Four nodes Harvester cluster status, before delete one of the control-plane node
n1-221021:/etc # kubectl get nodes NAME STATUS ROLES AGE VERSION n1-221021 Ready control-plane,etcd,master 17h v1.24.7+rke2r1 n2-221021 Ready control-plane,etcd,master 16h v1.24.7+rke2r1 n3-221021 Ready control-plane,etcd,master 15h v1.24.7+rke2r1 n4-221021 Ready <none> 4m10s v1.24.7+rke2r1
-
Delete the third control-plane node, the 4th node can be promoted to control-plane role
n1-221021:/etc # kubectl get nodes NAME STATUS ROLES AGE VERSION n1-221021 Ready control-plane,etcd,master 17h v1.24.7+rke2r1 n2-221021 Ready control-plane,etcd,master 16h v1.24.7+rke2r1 n4-221021 Ready control-plane,etcd,master 11m v1.24.7+rke2r1
n1-221021:/etc # kubectl get machines -A NAMESPACE NAME CLUSTER NODENAME PROVIDERID PHASE AGE VERSION fleet-local custom-00c844d92e49 local n4-221021 rke2://n4-221021 Running 12m fleet-local custom-580f66b2735d local n2-221021 rke2://n2-221021 Running 16h fleet-local custom-6c0eaa9d5d67 local n1-221021 rke2://n1-221021 Running 17h