Prerequisites for RMA Process
For GR deployment, the node-monitor pods starts automatically. During RMA procedure, the node-monitor pod automatically shutdown the rack if multi-compute failure is detected when the node is drain and deleted.
For more information on RMA (Return Merchandise Authorization), see SMI Cluster RMA section in the Ultra Cloud Core Subscriber Microservices Infrastructure - Operations Guide.
Before starting RMA process, perform the following:
-
Switch the role for both the instance to other rack using
geo switch-role role
command and make sure the target rack for RMA is in STANDBY_ERROR role for both the instances. -
Disable the node-monitor pod.
-
Take the backup of daemonsets.
kubectl get daemonsets node-monitor -n cn -o yaml > node-monitor.yaml
-
Delete node-monitor pods.
kubectl delete daemonsets node-monitor -n cn
-
-
Continue with RMA procedure. For more information, see the link.
Once RMA procedure is complete, check if the node-monitor pods are already spawned.
kubectl get pods -n cn -o wide | grep node-monitor
If the node-monitor pods have not started, restart them.
kubectl create -f node-monitor.yaml
Notenode-monitor.yaml file is same as in Step 2.a.
-
Correct the role for the instances accordingly.
Note | For both earlier and current SMI versions:
|