Replacing nodes

Procedure

1. Identify the node that you need to replace.

2. Mark the node as unschedulable:

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

   <node_name>

   Specify the name of node that you need to replace.

3. Drain the node:

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap
   Important

   This activity might take at least 5 - 10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when you label the new node, and it is functional.

4. Delete the node:

   $ oc delete nodes <node_name>

   Copy to Clipboard Toggle word wrap
5. Create a new Amazon Web Service (AWS) machine instance with the required infrastructure. See Platform requirements.
6. Create a new OpenShift Container Platform node using the new AWS machine instance.

7. Check for the Certificate Signing Requests (CSRs) related to OpenShift Container Platform that are in Pending state:

   $ oc get csr

   Copy to Clipboard Toggle word wrap

8. Approve all the required OpenShift Container Platform CSRs for the new node:

   $ oc adm certificate approve <certificate_name>

   Copy to Clipboard Toggle word wrap

   <certificate_name>

   Specify the name of the CSR.

9. Click Compute → Nodes. Confirm that the new node is in Ready state.

10. Apply the OpenShift Data Foundation label to the new node using one of the following:

    From the user interface

    1. For the new node, click Action Menu (⋮) → Edit Labels.
    2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

    From the command-line interface

    • Apply the OpenShift Data Foundation label to the new node:

    $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

    Copy to Clipboard Toggle word wrap

    <new_node_name>

    Specify the name of the new node.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Log in to the OpenShift Web Console, and click Compute → Nodes.
2. Identify the node that you need to replace. Take a note of its Machine Name.

3. Mark the node as unschedulable:

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

   <node_name>

   Specify the name of node that you need to replace.

4. Drain the node:

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap
   Important

   This activity might take at least 5 - 10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when you label the new node, and it is functional.

5. Click Compute → Machines. Search for the required machine.
6. Besides the required machine, click Action menu (⋮) → Delete Machine.
7. Click Delete to confirm that the machine is deleted. A new machine is automatically created.

8. Wait for the new machine to start and transition into Running state.

   Important

   This activity might take at least 5 - 10 minutes or more.

9. Click Compute → Nodes. Confirm that the new node is in Ready state.

10. Apply the OpenShift Data Foundation label to the new node:

    From the user interface

    1. For the new node, click Action Menu (⋮) → Edit Labels.
    2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

    From the command-line interface

    • Apply the OpenShift Data Foundation label to the new node:

    $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

    Copy to Clipboard Toggle word wrap

    <new_node_name>

    Specify the name of the new node.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Identify the Amazon Web Service (AWS) machine instance of the node that you need to replace.
2. Log in to AWS, and terminate the AWS machine instance that you identified.
3. Create a new AWS machine instance with the required infrastructure. See Platform requirements.
4. Create a new OpenShift Container Platform node using the new AWS machine instance.

5. Check for the Certificate Signing Requests (CSRs) related to OpenShift Container Platform that are in Pending state:

   $ oc get csr

   Copy to Clipboard Toggle word wrap

6. Approve all the required OpenShift Container Platform CSRs for the new node:

   $ oc adm certificate approve <certificate_name>

   Copy to Clipboard Toggle word wrap

   <certificate_name>

   Specify the name of the CSR.

7. Click Compute → Nodes. Confirm that the new node is in Ready state.

8. Apply the OpenShift Data Foundation label to the new node using any one of the following:

   From the user interface

   1. For the new node, click Action Menu (⋮) → Edit Labels.
   2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

   From the command-line interface

   • Execute the following command to apply the OpenShift Data Foundation label to the new node:

   $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

   Copy to Clipboard Toggle word wrap

   <new_node_name>

   Specify the name of the new node.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Log in to the OpenShift Web Console, and click Compute → Nodes.
2. Identify the faulty node, and click on its Machine Name.
3. Click Actions → Edit Annotations, and click Add More.
4. Add machine.openshift.io/exclude-node-draining, and click Save.
5. Click Actions → Delete Machine, and click Delete.

6. A new machine is automatically created, wait for new machine to start.

   Important

   This activity might take at least 5 - 10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when you label the new node, and it is functional.

7. Click Compute → Nodes. Confirm that the new node is in Ready state.

8. Apply the OpenShift Data Foundation label to the new node using any one of the following:

   From the user interface

   1. For the new node, click Action Menu (⋮) → Edit Labels.
   2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

   From the command-line interface

   • Apply the OpenShift Data Foundation label to the new node:

   $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

   Copy to Clipboard Toggle word wrap

   <new_node_name>

   Specify the name of the new node.

9. Optional: If the failed Amazon Web Service (AWS) instance is not removed automatically, terminate the instance from the AWS console.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Identify the node and its Virtual Machine (VM) that you need replace.

2. Mark the node as unschedulable:

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

   <node_name>

   Specify the name of node that you need to replace.

3. Drain the node:

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap
   Important

   This activity might take at least 5 - 10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when you label the new node, and it is functional.

4. Delete the node:

   $ oc delete nodes <node_name>

   Copy to Clipboard Toggle word wrap

5. Log in to VMware vSphere, and terminate the VM that you identified:

   Important

   Delete the VM only from the inventory and not from the disk.

6. Create a new VM on VMware vSphere with the required infrastructure. See Platform requirements.
7. Create a new OpenShift Container Platform worker node using the new VM.

8. Check for the Certificate Signing Requests (CSRs) related to OpenShift Container Platform that are in Pending state:

   $ oc get csr

   Copy to Clipboard Toggle word wrap

9. Approve all the required OpenShift Container Platform CSRs for the new node:

   $ oc adm certificate approve <certificate_name>

   Copy to Clipboard Toggle word wrap

   <certificate_name>

   Specify the name of the CSR.

10. Click Compute → Nodes. Confirm that the new node is in Ready state.

11. Apply the OpenShift Data Foundation label to the new node using any one of the following:

    From the user interface

    1. For the new node, click Action Menu (⋮) → Edit Labels.
    2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

    From the command-line interface

    • Apply the OpenShift Data Foundation label to the new node:

    $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

    Copy to Clipboard Toggle word wrap

    <new_node_name>

    Specify the name of the new node.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Log in to the OpenShift Web Console, and click Compute → Nodes.
2. Identify the node that you need to replace. Take a note of its Machine Name.

3. Mark the node as unschedulable:

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

   <node_name>

   Specify the name of node that you need to replace.

4. Drain the node:

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap
   Important

   This activity might take at least 5 - 10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when you label the new node, and it is functional.

5. Click Compute → Machines. Search for the required machine.
6. Besides the required machine, click Action menu (⋮) → Delete Machine.
7. Click Delete to confirm the machine is deleted. A new machine is automatically created.

8. Wait for the new machine to start and transition into Running state.

   Important

   This activity might take at least 5 - 10 minutes or more.

9. Click Compute → Nodes. Confirm that the new node is in Ready state.

10. Apply the OpenShift Data Foundation label to the new node using any one of the following:

    From the user interface

    1. For the new node, click Action Menu (⋮) → Edit Labels.
    2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

    From the command-line interface

    • Apply the OpenShift Data Foundation label to the new node:

    $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

    Copy to Clipboard Toggle word wrap

    <new_node_name>

    Specify the name of the new node.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Identify the node and its Virtual Machine (VM) that you need to replace.

2. Delete the node:

   $ oc delete nodes <node_name>

   Copy to Clipboard Toggle word wrap

   <node_name>

   Specify the name of node that you need to replace.

3. Log in to VMware vSphere and terminate the VM that you identified.

   Important

   Delete the VM only from the inventory and not from the disk.

4. Create a new VM on VMware vSphere with the required infrastructure. See Platform requirements.
5. Create a new OpenShift Container Platform worker node using the new VM.

6. Check for the Certificate Signing Requests (CSRs) related to OpenShift Container Platform that are in Pending state:

   $ oc get csr

   Copy to Clipboard Toggle word wrap

7. Approve all the required OpenShift Container Platform CSRs for the new node:

   $ oc adm certificate approve <certificate_name>

   Copy to Clipboard Toggle word wrap

   <certificate_name>

   Specify the name of the CSR.

8. Click Compute → Nodes. Confirm that the new node is in Ready state.

9. Apply the OpenShift Data Foundation label to the new node using any one of the following:

   From the user interface

   1. For the new node, click Action Menu (⋮) → Edit Labels.
   2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

   From the command-line interface

   • Apply the OpenShift Data Foundation label to the new node:

   $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

   Copy to Clipboard Toggle word wrap

   <new_node_name>

   Specify the name of the new node.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Log in to the OpenShift Web Console, and click Compute → Nodes.
2. Identify the faulty node, and click on its Machine Name.
3. Click Actions → Edit Annotations, and click Add More.
4. Add machine.openshift.io/exclude-node-draining, and click Save.
5. Click Actions → Delete Machine, and click Delete.

6. A new machine is automatically created. Wait for te new machine to start.

   Important

   This activity might take at least 5 - 10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when you label the new node, and it is functional.

7. Click Compute → Nodes. Confirm that the new node is in Ready state.

8. Apply the OpenShift Data Foundation label to the new node using any one of the following:

   From the user interface

   1. For the new node, click Action Menu (⋮) → Edit Labels.
   2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

   From the command-line interface

   • Apply the OpenShift Data Foundation label to the new node:

   $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

   Copy to Clipboard Toggle word wrap

   <new_node_name>

   Specify the name of the new node.

9. Optional: If the failed Virtual Machine (VM) is not removed automatically, terminate the VM from VMware vSphere.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Log in to the OpenShift Web Console, and click Compute → Nodes.
2. Identify the node that you need to replace. Take a note of its Machine Name.

3. Mark the node as unschedulable:

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

   <node_name>

   Specify the name of node that you need to replace.

4. Drain the node:

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap
   Important

   This activity might take at least 5 - 10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when you label the new node, and it is functional.

5. Click Compute → Machines. Search for the required machine.
6. Besides the required machine, click the Action menu (⋮) → Delete Machine.
7. Click Delete to confirm the machine is deleted. A new machine is automatically created.

8. Wait for the new machine to start and transition into Running state.

   Important

   This activity might take at least 5 - 10 minutes or more.

9. Click Compute → Nodes. Confirm that the new node is in Ready state.

10. Apply the OpenShift Data Foundation label to the new node using any one of the following:

    From the user interface

    1. For the new node, click Action Menu (⋮) → Edit Labels.
    2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

    From the command-line interface

    • Execute the following command to apply the OpenShift Data Foundation label to the new node:

    $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

    Copy to Clipboard Toggle word wrap

    <new_node_name>

    Specify the name of the new node.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads→ Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Log in to the OpenShift Web Console, and click Compute → Nodes.
2. Identify the faulty node, and click on its Machine Name.
3. Click Actions → Edit Annotations, and click Add More.
4. Add machine.openshift.io/exclude-node-draining, and click Save.
5. Click Actions → Delete Machine, and click Delete.

6. A new machine is automatically created. Wait for the new machine to start.

   Important

   This activity might take at least 5 - 10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when you label the new node, and it is functional.

7. Click Compute → Nodes. Confirm that the new node is in Ready state.

8. Apply the OpenShift Data Foundation label to the new node using any one of the following:

   From the user interface

   1. For the new node, click Action Menu (⋮) → Edit Labels.
   2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

   From the command-line interface

   • Apply the OpenShift Data Foundation label to the new node:

   $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

   Copy to Clipboard Toggle word wrap

   <new_node_name>

   Specify the name of the new node.

9. Optional: If the failed Azure instance is not removed automatically, terminate the instance from the Azure console.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that new the Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Log in to OpenShift Web Console and click Compute → Nodes.
2. Identify the node that needs to be replaced. Take a note of its Machine Name.

3. Mark the node as unschedulable using the following command:

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

4. Drain the node using the following command:

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap
   Important

   This activity may take at least 5-10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when the new node is labeled and functional.

5. Click Compute → Machines. Search for the required machine.
6. Besides the required machine, click the Action menu (⋮) → Delete Machine.
7. Click Delete to confirm the machine deletion. A new machine is automatically created.

8. Wait for new machine to start and transition into Running state.

   Important

   This activity may take at least 5-10 minutes or more.

9. Click Compute → Nodes, confirm if the new node is in Ready state.

10. Apply the OpenShift Data Foundation label to the new node using any one of the following:

    From User interface

    1. For the new node, click Action Menu (⋮) → Edit Labels
    2. Add cluster.ocs.openshift.io/openshift-storage and click Save.

    From Command line interface

    • Execute the following command to apply the OpenShift Data Foundation label to the new node:

      $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

      Copy to Clipboard Toggle word wrap

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that the new Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Log in to OpenShift Web Console and click Compute → Nodes.
2. Identify the faulty node and click on its Machine Name.
3. Click Actions → Edit Annotations, and click Add More.
4. Add machine.openshift.io/exclude-node-draining and click Save.
5. Click Actions → Delete Machine, and click Delete.

6. A new machine is automatically created, wait for new machine to start.

   Important

   This activity may take at least 5-10 minutes or more. Ceph errors generated during this period are temporary and are automatically resolved when the new node is labeled and functional.

7. Click Compute → Nodes, confirm if the new node is in Ready state.

8. Apply the OpenShift Data Foundation label to the new node using any one of the following:

   From the web user interface

   1. For the new node, click Action Menu (⋮) → Edit Labels
   2. Add cluster.ocs.openshift.io/openshift-storage and click Save.

   From the command line interface

   • Apply the OpenShift Data Foundation label to the new node:

   $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

   Copy to Clipboard Toggle word wrap

   <new_node_name>

   Specify the name of the new node.

9. Optional: If the failed Google Cloud instance is not removed automatically, terminate the instance from Google Cloud console.

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*
3. Verify that all the other required OpenShift Data Foundation pods are in Running state.

4. Verify that new the Object Storage Device (OSD) pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Identify the node, and get the labels on the node that you need to replace:

   $ oc get nodes --show-labels | grep <node_name>

   Copy to Clipboard Toggle word wrap

   <node_name>

   Specify the name of node that you need to replace.

2. Identify the monitor pod (if any), and OSDs that are running in the node that you need to replace:

   $ oc get pods -n openshift-storage -o wide | grep -i <node_name>

   Copy to Clipboard Toggle word wrap

3. Scale down the deployments of the pods identified in the previous step:

   For example:

   $ oc scale deployment rook-ceph-mon-c --replicas=0 -n openshift-storage

   Copy to Clipboard Toggle word wrap

   $ oc scale deployment rook-ceph-osd-0 --replicas=0 -n openshift-storage

   Copy to Clipboard Toggle word wrap

   $ oc scale deployment --selector=app=rook-ceph-crashcollector,node_name=<node_name>  --replicas=0 -n openshift-storage

   Copy to Clipboard Toggle word wrap

4. Mark the node as unschedulable:

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

5. Drain the node:

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap

6. Delete the node:

   $ oc delete node <node_name>

   Copy to Clipboard Toggle word wrap

7. Get a new bare-metal machine with the required infrastructure. See Installing on bare metal.

   Important

   For information about how to replace a master node when you have installed OpenShift Data Foundation on a three-node OpenShift compact bare-metal cluster, see the Backup and Restore guide in the OpenShift Container Platform documentation.

8. Create a new OpenShift Container Platform node using the new bare-metal machine.

9. Check for the Certificate Signing Requests (CSRs) related to OpenShift Container Platform that are in Pending state:

   $ oc get csr

   Copy to Clipboard Toggle word wrap

10. Approve all the required OpenShift Container Platform CSRs for the new node:

    $ oc adm certificate approve <certificate_name>

    Copy to Clipboard Toggle word wrap

    <certificate_name>

    Specify the name of the CSR.

11. Click Compute → Nodes in the OpenShift Web Console. Confirm that the new node is in Ready state.

12. Apply the OpenShift Data Foundation label to the new node using any one of the following:

    From the user interface

    1. For the new node, click Action Menu (⋮) → Edit Labels.
    2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

    From the command-line interface

    • Apply the OpenShift Data Foundation label to the new node:

    $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

    Copy to Clipboard Toggle word wrap

    <new_node_name>

    Specify the name of the new node.

13. Identify the namespace where OpenShift local storage operator is installed, and assign it to the local_storage_project variable:

    $ local_storage_project=$(oc get csv --all-namespaces | awk '{print $1}' | grep local)

    Copy to Clipboard Toggle word wrap

    For example:

    $ local_storage_project=$(oc get csv --all-namespaces | awk '{print $1}' | grep local)

    Copy to Clipboard Toggle word wrap

    echo $local_storage_project

    Copy to Clipboard Toggle word wrap

    Example output:

    openshift-local-storage

    Copy to Clipboard Toggle word wrap

14. Add a new worker node to the localVolumeDiscovery and localVolumeSet.

    1. Update the localVolumeDiscovery definition to include the new node, and remove the failed node:

       # oc edit -n $local_storage_project localvolumediscovery auto-discover-devices

       Copy to Clipboard Toggle word wrap

       Example output:

       [...]
          nodeSelector:
           nodeSelectorTerms:
             - matchExpressions:
                 - key: kubernetes.io/hostname
                   operator: In
                   values:
                   - server1.example.com
                   - server2.example.com
                   #- server3.example.com
                   - newnode.example.com
       [...]

       Copy to Clipboard Toggle word wrap

       Remember to save before exiting the editor.

       In this example, server3.example.com is removed, and newnode.example.com is the new node.

    2. Determine the localVolumeSet to edit:

       # oc get -n $local_storage_project localvolumeset

       Copy to Clipboard Toggle word wrap

       Example output:

       NAME          AGE
       localblock   25h

       Copy to Clipboard Toggle word wrap

    3. Update the localVolumeSet definition to include the new node, and remove the failed node:

       # oc edit -n $local_storage_project localvolumeset localblock

       Copy to Clipboard Toggle word wrap

       Example output:

       [...]
          nodeSelector:
           nodeSelectorTerms:
             - matchExpressions:
                 - key: kubernetes.io/hostname
                   operator: In
                   values:
                   - server1.example.com
                   - server2.example.com
                   #- server3.example.com
                   - newnode.example.com
       [...]

       Copy to Clipboard Toggle word wrap

       Remember to save before exiting the editor.

       In the this example, server3.example.com is removed and newnode.example.com is the new node.

15. Verify that the new localblock Persistent Volume (PV) is available:

    $oc get pv | grep localblock | grep Available

    Copy to Clipboard Toggle word wrap

    Example output:

    local-pv-551d950     512Gi    RWO    Delete  Available
    localblock     26s

    Copy to Clipboard Toggle word wrap

16. Navigate to the openshift-storage project:

    $ oc project openshift-storage

    Copy to Clipboard Toggle word wrap

17. Remove the failed OSD from the cluster. You can specify multiple failed OSDs if required:

    $ oc process -n openshift-storage ocs-osd-removal \
    -p FAILED_OSD_IDS=<failed_osd_id> | oc create -f -

    Copy to Clipboard Toggle word wrap

    <failed_osd_id>

    Is the integer in the pod name immediately after the rook-ceph-osd prefix.

    You can add comma separated OSD IDs in the command to remove more than one OSD, for example, FAILED_OSD_IDS=0,1,2.

    The FORCE_OSD_REMOVAL value must be changed to true in clusters that only have three OSDs, or clusters with insufficient space to restore all three replicas of the data after the OSD is removed.

18. Verify that the OSD was removed successfully by checking the status of the ocs-osd-removal-job pod.

    A status of Completed confirms that the OSD removal job succeeded.

    # oc get pod -l job-name=ocs-osd-removal-job -n openshift-storage

    Copy to Clipboard Toggle word wrap

19. Ensure that the OSD removal is completed.

    $ oc logs -l job-name=ocs-osd-removal-job -n openshift-storage --tail=-1 | egrep -i 'completed removal'

    Copy to Clipboard Toggle word wrap

    Example output:

    2022-05-10 06:50:04.501511 I | cephosd: completed removal of OSD 0

    Copy to Clipboard Toggle word wrap
    Important

    If the ocs-osd-removal-job fails, and the pod is not in the expected Completed state, check the pod logs for further debugging:

    For example:

    # oc logs -l job-name=ocs-osd-removal-job -n openshift-storage --tail=-1

    Copy to Clipboard Toggle word wrap

20. Identify the Persistent Volume (PV) associated with the Persistent Volume Claim (PVC):

    # oc get pv -L kubernetes.io/hostname | grep localblock | grep Released

    Copy to Clipboard Toggle word wrap

    Example output:

    local-pv-d6bf175b  1490Gi  RWO  Delete  Released  openshift-storage/ocs-deviceset-0-data-0-6c5pw  localblock  2d22h  compute-1

    Copy to Clipboard Toggle word wrap

    If there is a PV in Released state, delete it:

    # oc delete pv <persistent_volume>

    Copy to Clipboard Toggle word wrap

    For example:

    # oc delete pv local-pv-d6bf175b

    Copy to Clipboard Toggle word wrap

    Example output:

    persistentvolume "local-pv-d9c5cbd6" deleted

    Copy to Clipboard Toggle word wrap

21. Identify the crashcollector pod deployment:

    $ oc get deployment --selector=app=rook-ceph-crashcollector,node_name=<failed_node_name> -n openshift-storage

    Copy to Clipboard Toggle word wrap

    If there is an existing crashcollector pod deployment, delete it:

    $ oc delete deployment --selector=app=rook-ceph-crashcollector,node_name=<failed_node_name> -n openshift-storage

    Copy to Clipboard Toggle word wrap

22. Delete the ocs-osd-removal-job:

    # oc delete -n openshift-storage job ocs-osd-removal-job

    Copy to Clipboard Toggle word wrap

    Example output:

    job.batch "ocs-osd-removal-job" deleted

    Copy to Clipboard Toggle word wrap

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*

3. Verify that all other required OpenShift Data Foundation pods are in Running state.

   Ensure that the new incremental mon is created, and is in the Running state:

   $ oc get pod -n openshift-storage | grep mon

   Copy to Clipboard Toggle word wrap

   Example output:

   rook-ceph-mon-a-cd575c89b-b6k66         2/2     Running
   0          38m
   rook-ceph-mon-b-6776bc469b-tzzt8        2/2     Running
   0          38m
   rook-ceph-mon-d-5ff5d488b5-7v8xh        2/2     Running
   0          4m8s

   Copy to Clipboard Toggle word wrap

   OSD and monitor pod might take several minutes to get to the Running state.

4. Verify that new OSD pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Identify the node, and get the labels on the node that you need to replace:

   $ oc get nodes --show-labels | grep <node_name>

   Copy to Clipboard Toggle word wrap

   <node_name>

   Specify the name of node that you need to replace.

2. Identify the monitor pod (if any), and OSDs that are running in the node that you need to replace:

   $ oc get pods -n openshift-storage -o wide | grep -i <node_name>

   Copy to Clipboard Toggle word wrap

3. Scale down the deployments of the pods identified in the previous step:

   For example:

   $ oc scale deployment rook-ceph-mon-c --replicas=0 -n openshift-storage

   Copy to Clipboard Toggle word wrap

   $ oc scale deployment rook-ceph-osd-0 --replicas=0 -n openshift-storage

   Copy to Clipboard Toggle word wrap

   $ oc scale deployment --selector=app=rook-ceph-crashcollector,node_name=<node_name>  --replicas=0 -n openshift-storage

   Copy to Clipboard Toggle word wrap

4. Mark the node as unschedulable:

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

5. Remove the pods which are in Terminating state:

   $ oc get pods -A -o wide | grep -i <node_name> |  awk '{if ($4 == "Terminating") system ("oc -n " $1 " delete pods " $2  " --grace-period=0 " " --force ")}'

   Copy to Clipboard Toggle word wrap

6. Drain the node:

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap

7. Delete the node:

   $ oc delete node <node_name>

   Copy to Clipboard Toggle word wrap

8. Get a new bare-metal machine with the required infrastructure. See Installing on bare metal.

   Important

   For information about how to replace a master node when you have installed OpenShift Data Foundation on a three-node OpenShift compact bare-metal cluster, see the Backup and Restore guide in the OpenShift Container Platform documentation.

9. Create a new OpenShift Container Platform node using the new bare-metal machine.

10. Check for the Certificate Signing Requests (CSRs) related to OpenShift Container Platform that are in Pending state:

    $ oc get csr

    Copy to Clipboard Toggle word wrap

11. Approve all the required OpenShift Container Platform CSRs for the new node:

    $ oc adm certificate approve <certificate_name>

    Copy to Clipboard Toggle word wrap

    <certificate_name>

    Specify the name of the CSR.

12. Click Compute → Nodes in the OpenShift Web Console. Confirm that the new node is in Ready state.

13. Apply the OpenShift Data Foundation label to the new node using any one of the following:

    From the user interface

    1. For the new node, click Action Menu (⋮) → Edit Labels.
    2. Add cluster.ocs.openshift.io/openshift-storage, and click Save.

    From the command-line interface

    • Apply the OpenShift Data Foundation label to the new node:

    $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

    Copy to Clipboard Toggle word wrap

    <new_node_name>

    Specify the name of the new node.

14. Identify the namespace where OpenShift local storage operator is installed, and assign it to the local_storage_project variable:

    $ local_storage_project=$(oc get csv --all-namespaces | awk '{print $1}' | grep local)

    Copy to Clipboard Toggle word wrap

    For example:

    $ local_storage_project=$(oc get csv --all-namespaces | awk '{print $1}' | grep local)

    Copy to Clipboard Toggle word wrap

    echo $local_storage_project

    Copy to Clipboard Toggle word wrap

    Example output:

    openshift-local-storage

    Copy to Clipboard Toggle word wrap

15. Add a new worker node to the localVolumeDiscovery and localVolumeSet.

    1. Update the localVolumeDiscovery definition to include the new node, and remove the failed node:

       # oc edit -n $local_storage_project localvolumediscovery auto-discover-devices

       Copy to Clipboard Toggle word wrap

       Example output:

       [...]
          nodeSelector:
           nodeSelectorTerms:
             - matchExpressions:
                 - key: kubernetes.io/hostname
                   operator: In
                   values:
                   - server1.example.com
                   - server2.example.com
                   #- server3.example.com
                   - newnode.example.com
       [...]

       Copy to Clipboard Toggle word wrap

       Remember to save before exiting the editor.

       In this example, server3.example.com is removed, and newnode.example.com is the new node.

    2. Determine the localVolumeSet to edit:

       # oc get -n $local_storage_project localvolumeset

       Copy to Clipboard Toggle word wrap

       Example output:

       NAME          AGE
       localblock   25h

       Copy to Clipboard Toggle word wrap

    3. Update the localVolumeSet definition to include the new node, and remove the failed node:

       # oc edit -n $local_storage_project localvolumeset localblock

       Copy to Clipboard Toggle word wrap

       Example output:

       [...]
          nodeSelector:
           nodeSelectorTerms:
             - matchExpressions:
                 - key: kubernetes.io/hostname
                   operator: In
                   values:
                   - server1.example.com
                   - server2.example.com
                   #- server3.example.com
                   - newnode.example.com
       [...]

       Copy to Clipboard Toggle word wrap

       Remember to save before exiting the editor.

       In the this example, server3.example.com is removed and newnode.example.com is the new node.

16. Verify that the new localblock Persistent Volume (PV) is available:

    $oc get pv | grep localblock | grep Available

    Copy to Clipboard Toggle word wrap

    Example output:

    local-pv-551d950     512Gi    RWO    Delete  Available
    localblock     26s

    Copy to Clipboard Toggle word wrap

17. Navigate to the openshift-storage project:

    $ oc project openshift-storage

    Copy to Clipboard Toggle word wrap

18. Remove the failed OSD from the cluster. You can specify multiple failed OSDs if required:

    $ oc process -n openshift-storage ocs-osd-removal \
    -p FAILED_OSD_IDS=<failed_osd_id> | oc create -f -

    Copy to Clipboard Toggle word wrap

    <failed_osd_id>

    Is the integer in the pod name immediately after the rook-ceph-osd prefix.

    You can add comma separated OSD IDs in the command to remove more than one OSD, for example, FAILED_OSD_IDS=0,1,2.

    The FORCE_OSD_REMOVAL value must be changed to true in clusters that only have three OSDs, or clusters with insufficient space to restore all three replicas of the data after the OSD is removed.

19. Verify that the OSD was removed successfully by checking the status of the ocs-osd-removal-job pod.

    A status of Completed confirms that the OSD removal job succeeded.

    # oc get pod -l job-name=ocs-osd-removal-job -n openshift-storage

    Copy to Clipboard Toggle word wrap

20. Ensure that the OSD removal is completed.

    $ oc logs -l job-name=ocs-osd-removal-job -n openshift-storage --tail=-1 | egrep -i 'completed removal'

    Copy to Clipboard Toggle word wrap

    Example output:

    2022-05-10 06:50:04.501511 I | cephosd: completed removal of OSD 0

    Copy to Clipboard Toggle word wrap
    Important

    If the ocs-osd-removal-job fails, and the pod is not in the expected Completed state, check the pod logs for further debugging:

    For example:

    # oc logs -l job-name=ocs-osd-removal-job -n openshift-storage --tail=-1

    Copy to Clipboard Toggle word wrap

21. Identify the Persistent Volume (PV) associated with the Persistent Volume Claim (PVC):

    # oc get pv -L kubernetes.io/hostname | grep localblock | grep Released

    Copy to Clipboard Toggle word wrap

    Example output:

    local-pv-d6bf175b  1490Gi  RWO  Delete  Released  openshift-storage/ocs-deviceset-0-data-0-6c5pw  localblock  2d22h  compute-1

    Copy to Clipboard Toggle word wrap

    If there is a PV in Released state, delete it:

    # oc delete pv <persistent_volume>

    Copy to Clipboard Toggle word wrap

    For example:

    # oc delete pv local-pv-d6bf175b

    Copy to Clipboard Toggle word wrap

    Example output:

    persistentvolume "local-pv-d9c5cbd6" deleted

    Copy to Clipboard Toggle word wrap

22. Identify the crashcollector pod deployment:

    $ oc get deployment --selector=app=rook-ceph-crashcollector,node_name=<failed_node_name> -n openshift-storage

    Copy to Clipboard Toggle word wrap

    If there is an existing crashcollector pod deployment, delete it:

    $ oc delete deployment --selector=app=rook-ceph-crashcollector,node_name=<failed_node_name> -n openshift-storage

    Copy to Clipboard Toggle word wrap

23. Delete the ocs-osd-removal-job:

    # oc delete -n openshift-storage job ocs-osd-removal-job

    Copy to Clipboard Toggle word wrap

    Example output:

    job.batch "ocs-osd-removal-job" deleted

    Copy to Clipboard Toggle word wrap

Verification steps

1. Verify that the new node is present in the output:

   $ oc get nodes --show-labels | grep cluster.ocs.openshift.io/openshift-storage= |cut -d' ' -f1

   Copy to Clipboard Toggle word wrap

2. Click Workloads → Pods. Confirm that at least the following pods on the new node are in Running state:

   • csi-cephfsplugin-*
   • csi-rbdplugin-*

3. Verify that all other required OpenShift Data Foundation pods are in Running state.

   Ensure that the new incremental mon is created, and is in the Running state:

   $ oc get pod -n openshift-storage | grep mon

   Copy to Clipboard Toggle word wrap

   Example output:

   rook-ceph-mon-a-cd575c89b-b6k66         2/2     Running
   0          38m
   rook-ceph-mon-b-6776bc469b-tzzt8        2/2     Running
   0          38m
   rook-ceph-mon-d-5ff5d488b5-7v8xh        2/2     Running
   0          4m8s

   Copy to Clipboard Toggle word wrap

   OSD and monitor pod might take several minutes to get to the Running state.

4. Verify that new OSD pods are running on the replacement node:

   $ oc get pods -o wide -n openshift-storage| egrep -i <new_node_name> | egrep osd

   Copy to Clipboard Toggle word wrap

5. Optional: If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

   For each of the new nodes identified in the previous step, do the following:

   1. Create a debug pod and open a chroot environment for the one or more selected hosts:

      $ oc debug node/<node_name>

      Copy to Clipboard Toggle word wrap

      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Display the list of available block devices:

      $ lsblk

      Copy to Clipboard Toggle word wrap

      Check for the crypt keyword beside the one or more ocs-deviceset names.

6. If the verification steps fail, contact Red Hat Support.

Procedure

1. Identify the node and get labels on the node to be replaced. Make a note of the rack label.

   $ oc get nodes --show-labels | grep <node_name>

   Copy to Clipboard Toggle word wrap

2. Identify the mon (if any) and object storage device (OSD) pods that are running in the node to be replaced.

   $ oc get pods -n openshift-storage -o wide | grep -i <node_name>

   Copy to Clipboard Toggle word wrap

3. Scale down the deployments of the pods identified in the previous step.

   For example:

   $ oc scale deployment rook-ceph-mon-c --replicas=0 -n openshift-storage
   $ oc scale deployment rook-ceph-osd-0 --replicas=0 -n openshift-storage
   $ oc scale deployment --selector=app=rook-ceph-crashcollector,node_name=<node_name>  --replicas=0 -n openshift-storage

   Copy to Clipboard Toggle word wrap

4. Mark the nodes as unschedulable.

   $ oc adm cordon <node_name>

   Copy to Clipboard Toggle word wrap

5. Remove the pods which are in the Terminating state.

   $ oc get pods -A -o wide | grep -i <node_name> |  awk '{if ($4 == "Terminating") system ("oc -n " $1 " delete pods " $2  " --grace-period=0 " " --force ")}'

   Copy to Clipboard Toggle word wrap

6. Drain the node.

   $ oc adm drain <node_name> --force --delete-emptydir-data=true --ignore-daemonsets

   Copy to Clipboard Toggle word wrap

7. Delete the node.

   $ oc delete node <node_name>

   Copy to Clipboard Toggle word wrap
8. Get a new IBM Z storage node as a replacement.

9. Check for certificate signing requests (CSRs) related to OpenShift Data Foundation that are in Pending state:

   $ oc get csr

   Copy to Clipboard Toggle word wrap

10. Approve all required OpenShift Data Foundation CSRs for the new node:

    $ oc adm certificate approve <Certificate_Name>

    Copy to Clipboard Toggle word wrap
11. Click Compute → Nodes in OpenShift Web Console, confirm if the new node is in Ready state.

12. Apply the openshift-storage label to the new node using any one of the following:

    From User interface

    1. For the new node, click Action Menu (⋮) → Edit Labels
    2. Add cluster.ocs.openshift.io/openshift-storage and click Save.

    From Command line interface

    • Execute the following command to apply the OpenShift Data Foundation label to the new node:

    $ oc label node <new_node_name> cluster.ocs.openshift.io/openshift-storage=""

    Copy to Clipboard Toggle word wrap

13. Add a new worker node to localVolumeDiscovery and localVolumeSet.

    1. Update the localVolumeDiscovery definition to include the new node and remove the failed node.

       # oc edit -n local-storage-project localvolumediscovery auto-discover-devices
       [...]
          nodeSelector:
           nodeSelectorTerms:
             - matchExpressions:
                 - key: kubernetes.io/hostname
                   operator: In
                   values:
                   - server1.example.com
                   - server2.example.com
                   #- server3.example.com
                   - newnode.example.com
       [...]

       Copy to Clipboard Toggle word wrap

       Remember to save before exiting the editor.

       In the above example, server3.example.com was removed and newnode.example.com is the new node.

    2. Determine which localVolumeSet to edit.

       Replace local-storage-project in the following commands with the name of your local storage project. The default project name is openshift-local-storage in OpenShift Data Foundation 4.6 and later. Previous versions use local-storage by default.

       # oc get -n local-storage-project localvolumeset
       NAME          AGE
       localblock   25h

       Copy to Clipboard Toggle word wrap

    3. Update the localVolumeSet definition to include the new node and remove the failed node.

       # oc edit -n local-storage-project localvolumeset localblock
       [...]
          nodeSelector:
           nodeSelectorTerms:
             - matchExpressions:
                 - key: kubernetes.io/hostname
                   operator: In
                   values:
                   - server1.example.com
                   - server2.example.com
                   #- server3.example.com
                   - newnode.example.com
       [...]

       Copy to Clipboard Toggle word wrap

       Remember to save before exiting the editor.

       In the above example, server3.example.com was removed and newnode.example.com is the new node.

14. Verify that the new localblock PV is available.

    $ oc get pv | grep localblock
              CAPA- ACCESS RECLAIM                                STORAGE
    NAME      CITY  MODES  POLICY  STATUS     CLAIM               CLASS       AGE
    local-pv- 931Gi  RWO   Delete  Bound      openshift-storage/  localblock  25h
    3e8964d3                                  ocs-deviceset-2-0
                                              -79j94
    local-pv- 931Gi  RWO   Delete  Bound      openshift-storage/  localblock  25h
    414755e0                                  ocs-deviceset-1-0
                                              -959rp
    local-pv- 931Gi RWO Delete Available localblock 3m24s b481410
    local-pv- 931Gi  RWO   Delete  Bound      openshift-storage/  localblock  25h
    d9c5cbd6                                  ocs-deviceset-0-0
                                              -nvs68

    Copy to Clipboard Toggle word wrap

15. Change to the openshift-storage project.

    $ oc project openshift-storage

    Copy to Clipboard Toggle word wrap

16. Remove the failed OSD from the cluster. You can specify multiple failed OSDs if required.

    1. Identify the PVC as afterwards we need to delete PV associated with that specific PVC.

       $ osd_id_to_remove=1
       $ oc get -n openshift-storage -o yaml deployment rook-ceph-osd-${osd_id_to_remove} | grep ceph.rook.io/pvc

       Copy to Clipboard Toggle word wrap

       where, osd_id_to_remove is the integer in the pod name immediately after the rook-ceph-osd prefix. In this example, the deployment name is rook-ceph-osd-1.

       Example output:

       ceph.rook.io/pvc: ocs-deviceset-localblock-0-data-0-g2mmc
           ceph.rook.io/pvc: ocs-deviceset-localblock-0-data-0-g2mmc

       Copy to Clipboard Toggle word wrap

       In this example, the PVC name is ocs-deviceset-localblock-0-data-0-g2mmc.

    2. Remove the failed OSD from the cluster.

       $ oc process -n openshift-storage ocs-osd-removal -p FAILED_OSD_IDS=${osd_id_to_remove} |oc create -f -

       Copy to Clipboard Toggle word wrap

       You can remove more than one OSD by adding comma separated OSD IDs in the command. (For example: FAILED_OSD_IDS=0,1,2)

       Warning

       This step results in OSD being completely removed from the cluster. Ensure that the correct value of osd_id_to_remove is provided.

17. Verify that the OSD was removed successfully by checking the status of the ocs-osd-removal pod.

    A status of Completed confirms that the OSD removal job succeeded.

    # oc get pod -l job-name=ocs-osd-removal-osd_id_to_remove -n openshift-storage

    Copy to Clipboard Toggle word wrap
    Note

    If ocs-osd-removal fails and the pod is not in the expected Completed state, check the pod logs for further debugging. For example:

    # oc logs -l job-name=ocs-osd-removal-osd_id_to_remove -n openshift-storage --tail=-1

    Copy to Clipboard Toggle word wrap

    It may be necessary to manually cleanup the removed OSD as follows:

    ceph osd crush remove osd.osd_id_to_remove
    ceph osd rm osd_id_to_remove
    ceph auth del osd.osd_id_to_remove
    ceph osd crush rm osd_id_to_remove

    Copy to Clipboard Toggle word wrap

18. Delete the PV associated with the failed node.

    1. Identify the PV associated with the PVC.

       The PVC name must be identical to the name that is obtained while removing the failed OSD from the cluster.

       # oc get pv -L kubernetes.io/hostname | grep localblock | grep Released
       local-pv-5c9b8982  500Gi  RWO  Delete  Released  openshift-storage/ocs-deviceset-localblock-0-data-0-g2mmc  localblock  24h  worker-0

       Copy to Clipboard Toggle word wrap

    2. If there is a PV in Released state, delete it.

       # oc delete pv <persistent-volume>

       Copy to Clipboard Toggle word wrap

       For example:

       # oc delete pv local-pv-5c9b8982
       persistentvolume "local-pv-5c9b8982" deleted

       Copy to Clipboard Toggle word wrap

19. Identify the crashcollector pod deployment.

    $ oc get deployment --selector=app=rook-ceph-crashcollector,node_name=<failed_node_name> -n openshift-storage

    Copy to Clipboard Toggle word wrap

    If there is an existing crashcollector pod deployment, delete it.

    $ oc delete deployment --selector=app=rook-ceph-crashcollector,node_name=<failed_node_name> -n openshift-storage

    Copy to Clipboard Toggle word wrap

20. Delete the ocs-osd-removal job.

    # oc delete job ocs-osd-removal-${osd_id_to_remove}

    Copy to Clipboard Toggle word wrap

    Example output:

    job.batch "ocs-osd-removal-0" deleted

    Copy to Clipboard Toggle word wrap