Deploying OpenShift Container Storage using Amazon Web Services

1. Log in to the Red Hat Enterprise Linux based node and open a terminal.

2. Verify that the node has access to the rhel-7-server-extras-rpms repository.

   # subscription-manager repos --list-enabled | grep rhel-7-server

   Copy to Clipboard Toggle word wrap

   If you do not see both rhel-7-server-rpms and rhel-7-server-extras-rpms in the output, or if there is no output, run the following commands to enable each repository.

   # subscription-manager repos --enable=rhel-7-server-rpms
   # subscription-manager repos --enable=rhel-7-server-extras-rpms

   Copy to Clipboard Toggle word wrap

3. Install the required packages.

   # yum install -y policycoreutils container-selinux

   Copy to Clipboard Toggle word wrap

4. Persistently enable container use of the Ceph file system in SELinux.

   # setsebool -P container_use_cephfs on

   Copy to Clipboard Toggle word wrap

Procedure

1. Click Operators → OperatorHub in the left pane of the OpenShift Web Console.
2. Use Filter by keyword text box or the filter list to search for OpenShift Container Storage from the list of operators.
3. Click OpenShift Container Storage.
4. On the OpenShift Container Storage operator page, click Install.

5. On the Install Operator page, ensure the following options are selected by default::

   1. Update Channel as stable-4.6
   2. Installation Mode as A specific namespace on the cluster
   3. Installed Namespace as Operator recommended namespace openshift-storage. If Namespace openshift-storage does not exist, it will be created during the operator installation.
   4. Select Enable operator recommended cluster monitoring on this namespace checkbox as this is required for cluster monitoring.

   5. Select Approval Strategy as Automatic or Manual. Approval Strategy is set to Automatic by default.

      • Approval Strategy as Automatic.

        Note

        When you select the Approval Strategy as Automatic, approval is not required either during fresh installation or when updating to the latest version of OpenShift Container Storage.

        1. Click Install
        2. Wait for the install to initiate. This may take up to 20 minutes.
        3. Click Operators → Installed Operators
        4. Ensure the Project is openshift-storage. By default, the Project is openshift-storage.
        5. Wait for the Status of OpenShift Container Storage to change to Succeeded.

      • Approval Strategy as Manual.

        Note

        When you select the Approval Strategy as Manual, approval is required during fresh installation or when updating to the latest version of OpenShift Container Storage.

        1. Click Install

        2. On the Manual approval required page, you can either click Approve or View Installed Operators in namespace openshift-storage to install the operator.

           Important

           Before you click either of the options, wait for a few minutes on the Manual approval required page until the install plan gets loaded in the window.

           Important

           If you choose to click Approve, you must review the install plan before you proceed.

           • If you click Approve.

             • Wait for a few minutes while the OpenShift Container Storage Operator is getting installed.
             • On the Installed operator - ready for use page, click View Operator.
             • Ensure the Project is openshift-storage. By default, the Project is openshift-storage.
             • Click Operators → Installed Operators
             • Wait for the Status of OpenShift Container Storage to change to Succeeded.

           • If you click View Installed Operators in namespace openshift-storage .

             • On the Installed Operators page, click ocs-operator.
             • On the Subscription Details page, click the Install Plan link.
             • On the InstallPlan Details page, click Preview Install Plan.
             • Review the install plan and click Approve.
             • Wait for the Status of the Components to change from Unknown to either Created or Present.
             • Click Operators → Installed Operators
             • Ensure the Project is openshift-storage. By default, the Project is openshift-storage.
             • Wait for the Status of OpenShift Container Storage to change to Succeeded.

Procedure

1. Click Operators → Installed Operators to view all the installed operators.

   Ensure that the Project selected is openshift-storage.

   Figure 1.1. OpenShift Container Storage Operator page

   

2. Click OpenShift Container Storage.

   Figure 1.2. Details tab of OpenShift Container Storage

   

3. Click Create Instance link of Storage Cluster.

   Figure 1.3. Create Storage Cluster page

   

4. On the Create Storage Cluster page, ensure that the following options are selected:

   1. In the Select Mode section, Internal mode is selected by default.
   2. Storage Class is set by default to gp2 for AWS.

   3. Select OpenShift Container Storage Service Capacity from drop down list.

      Note

      Once you select the initial storage capacity, cluster expansion will only be performed using the selected usable capacity (times 3 of raw storage).

   4. (Optional) In the Encryption section, set the toggle to Enabled to enable data encryption on the cluster.

   5. In the Nodes section, select at least three worker nodes from the available list for the use of OpenShift Container Storage service.

      For cloud platforms with multiple availability zones, ensure that the Nodes are spread across different Locations/availability zones.

      Note

      To find specific worker nodes in the cluster, you can filter nodes on the basis of Name or Label.

      • Name allows you to search by name of the node
      • Label allows you to search by selecting the predefined label

      If the nodes selected do not match the OpenShift Container Storage cluster requirement of an aggregated 30 CPUs and 72 GiB of RAM, a minimal cluster will be deployed. For minimum starting node requirements, see Resource requirements section in Planning guide.

5. Click Create.

   The Create button is enabled only after you select three nodes. A new storage cluster with three storage devices will be created, one per selected node. The default configuration uses a replication factor of 3.

Verification steps

1. Verify that the final Status of the installed storage cluster shows as Phase: Ready with a green tick mark.

   • Click Operators → Installed Operators → Storage Cluster link to view the storage cluster installation status.
   • Alternatively, when you are on the Operator Details tab, you can click on the Storage Cluster tab to view the status.
2. To verify that all components for OpenShift Container Storage are successfully installed, see Verifying your OpenShift Container Storage installation.

1. Understand the requirements for installing OpenShift Container Storage using local storage devices.

2. For Red Hat Enterprise Linux based hosts for worker nodes, enable file system access for containers on Red Hat Enterprise Linux based nodes.

   Note

   Skip this step for Red Hat Enterprise Linux CoreOS (RHCOS).

3. Install the Red Hat OpenShift Container Storage Operator.
4. Install Local Storage Operator.
5. Find the available storage devices.
6. Create OpenShift Container Storage cluster service on Amazon EC2 storage optimized - i3en.2xlarge instance type.

1. Log in to the Red Hat Enterprise Linux based node and open a terminal.

2. Verify that the node has access to the rhel-7-server-extras-rpms repository.

   # subscription-manager repos --list-enabled | grep rhel-7-server

   Copy to Clipboard Toggle word wrap

   If you do not see both rhel-7-server-rpms and rhel-7-server-extras-rpms in the output, or if there is no output, run the following commands to enable each repository.

   # subscription-manager repos --enable=rhel-7-server-rpms
   # subscription-manager repos --enable=rhel-7-server-extras-rpms

   Copy to Clipboard Toggle word wrap

3. Install the required packages.

   # yum install -y policycoreutils container-selinux

   Copy to Clipboard Toggle word wrap

4. Persistently enable container use of the Ceph file system in SELinux.

   # setsebool -P container_use_cephfs on

   Copy to Clipboard Toggle word wrap

Procedure

1. Click Operators → OperatorHub in the left pane of the OpenShift Web Console.
2. Use Filter by keyword text box or the filter list to search for OpenShift Container Storage from the list of operators.
3. Click OpenShift Container Storage.
4. On the OpenShift Container Storage operator page, click Install.

5. On the Install Operator page, ensure the following options are selected by default::

   1. Update Channel as stable-4.6
   2. Installation Mode as A specific namespace on the cluster
   3. Installed Namespace as Operator recommended namespace openshift-storage. If Namespace openshift-storage does not exist, it will be created during the operator installation.
   4. Select Enable operator recommended cluster monitoring on this namespace checkbox as this is required for cluster monitoring.

   5. Select Approval Strategy as Automatic or Manual. Approval Strategy is set to Automatic by default.

      • Approval Strategy as Automatic.

        Note

        When you select the Approval Strategy as Automatic, approval is not required either during fresh installation or when updating to the latest version of OpenShift Container Storage.

        1. Click Install
        2. Wait for the install to initiate. This may take up to 20 minutes.
        3. Click Operators → Installed Operators
        4. Ensure the Project is openshift-storage. By default, the Project is openshift-storage.
        5. Wait for the Status of OpenShift Container Storage to change to Succeeded.

      • Approval Strategy as Manual.

        Note

        When you select the Approval Strategy as Manual, approval is required during fresh installation or when updating to the latest version of OpenShift Container Storage.

        1. Click Install

        2. On the Manual approval required page, you can either click Approve or View Installed Operators in namespace openshift-storage to install the operator.

           Important

           Before you click either of the options, wait for a few minutes on the Manual approval required page until the install plan gets loaded in the window.

           Important

           If you choose to click Approve, you must review the install plan before you proceed.

           • If you click Approve.

             • Wait for a few minutes while the OpenShift Container Storage Operator is getting installed.
             • On the Installed operator - ready for use page, click View Operator.
             • Ensure the Project is openshift-storage. By default, the Project is openshift-storage.
             • Click Operators → Installed Operators
             • Wait for the Status of OpenShift Container Storage to change to Succeeded.

           • If you click View Installed Operators in namespace openshift-storage .

             • On the Installed Operators page, click ocs-operator.
             • On the Subscription Details page, click the Install Plan link.
             • On the InstallPlan Details page, click Preview Install Plan.
             • Review the install plan and click Approve.
             • Wait for the Status of the Components to change from Unknown to either Created or Present.
             • Click Operators → Installed Operators
             • Ensure the Project is openshift-storage. By default, the Project is openshift-storage.
             • Wait for the Status of OpenShift Container Storage to change to Succeeded.

Procedure

1. Log in to the OpenShift Web Console.
2. Click Operators → OperatorHub.
3. Type local storage in the Filter by keyword…​ box to search for Local Storage operator from the list of operators and click on it.

4. Click Install.

   Figure 2.1. Install Operator page

   

5. Set the following options on the Install Operator page:

   1. Update Channel as 4.6
   2. Installation Mode as A specific namespace on the cluster
   3. Installed Namespace as Operator recommended namespace openshift-local-storage.
   4. Approval Strategy as Automatic
6. Click Install.
7. Verify that the Local Storage Operator shows the Status as Succeeded.

Procedure

1. List and verify the name of the nodes with the OpenShift Container Storage label.

   $ oc get nodes -l cluster.ocs.openshift.io/openshift-storage=

   Copy to Clipboard Toggle word wrap

   Example output:

   NAME                                        STATUS   ROLES    AGE     VERSION
   ip-10-0-135-71.us-east-2.compute.internal    Ready    worker   6h45m   v1.16.2
   ip-10-0-145-125.us-east-2.compute.internal   Ready    worker   6h45m   v1.16.2
   ip-10-0-160-91.us-east-2.compute.internal    Ready    worker   6h45m   v1.16.2

   Copy to Clipboard Toggle word wrap

2. Log in to each node that is used for OpenShift Container Storage resources and find the unique by-id device name for each available raw block device.

   $ oc debug node/<node name>

   Copy to Clipboard Toggle word wrap

   Example output:

   $ oc debug node/ip-10-0-135-71.us-east-2.compute.internal
   Starting pod/ip-10-0-135-71us-east-2computeinternal-debug ...
   To use host binaries, run `chroot /host`
   Pod IP: 10.0.135.71
   If you don't see a command prompt, try pressing enter.
   sh-4.2# chroot /host
   sh-4.4# lsblk
   NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
   xvda                         202:0    0   120G  0 disk
   |-xvda1                      202:1    0   384M  0 part /boot
   |-xvda2                      202:2    0   127M  0 part /boot/efi
   |-xvda3                      202:3    0     1M  0 part
   `-xvda4                      202:4    0 119.5G  0 part
     `-coreos-luks-root-nocrypt 253:0    0 119.5G  0 dm   /sysroot
   nvme0n1                      259:0    0   2.3T  0 disk
   nvme1n1                      259:1    0   2.3T  0 disk

   Copy to Clipboard Toggle word wrap

   In this example, for the selected node, the local devices available are nvme0n1 and nvme1n1.

3. Identify the unique ID for each of the devices selected in Step 2.

   sh-4.4#  ls -l /dev/disk/by-id/ | grep Storage
   lrwxrwxrwx. 1 root root 13 Mar 17 16:24 nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441494EC -> ../../nvme0n1
   lrwxrwxrwx. 1 root root 13 Mar 17 16:24 nvme-Amazon_EC2_NVMe_Instance_Storage_AWS60382E5D7441494EC -> ../../nvme1n1

   Copy to Clipboard Toggle word wrap

   In the example above, the IDs for the two local devices are

   • nvme0n1: nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441494EC
   • nvme1n1: nvme-Amazon_EC2_NVMe_Instance_Storage_AWS60382E5D7441494EC
4. Repeat the above step to identify the device ID for all the other nodes that have the storage devices to be used by OpenShift Container Storage. See this Knowledge Base article for more details.

1. Create PVs by using the LocalVolume CR
2. Create a new StorageClass

Procedure

1. Create local persistent volumes (PVs) on the storage nodes using LocalVolume custom resource (CR).

   Example of LocalVolume CR local-storage-block.yaml using OpenShift Storage Container label as node selector and by-id device identifier:

   apiVersion: local.storage.openshift.io/v1
   kind: LocalVolume
   metadata:
     name: local-block
     namespace: openshift-local-storage
     labels:
       app: ocs-storagecluster
   spec:
     tolerations:
     - key: "node.ocs.openshift.io/storage"
       value: "true"
       effect: NoSchedule
     nodeSelector:
       nodeSelectorTerms:
         - matchExpressions:
             - key: cluster.ocs.openshift.io/openshift-storage
               operator: In
               values:
                 - ''
     storageClassDevices:
       - storageClassName: localblock
         volumeMode: Block
         devicePaths:
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441494EC   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS1F45C01D7E84FE3E9   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS136BC945B4ECB9AE4   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441464EP   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS1F45C01D7E84F43E7   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS136BC945B4ECB9AE8   # <-- modify this line

   Copy to Clipboard Toggle word wrap

   Each Amazon EC2 I3 instance has two disks and this example uses both disks on each node.

2. Create the LocalVolume CR.

   $ oc create -f local-storage-block.yaml

   Copy to Clipboard Toggle word wrap

   Example output:

   localvolume.local.storage.openshift.io/local-block created

   Copy to Clipboard Toggle word wrap

3. Check if the pods are created.

   $ oc -n openshift-local-storage get pods

   Copy to Clipboard Toggle word wrap

4. Check if the PVs are created.

   You must see a new PV for each of the local storage devices on the three worker nodes. Refer to the example in the Finding available storage devices section that shows two available storage devices per worker node with a size 2.3 TiB for each node.

   $ oc get pv

   Copy to Clipboard Toggle word wrap

   Example output:

   NAME               CAPACITY ACCESS MODES  RECLAIM POLICY STATUS       CLAIM     STORAGECLASS  REASON   AGE
   local-pv-1a46bc79  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-429d90ee  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-4d0a62e3  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-55c05d76  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-5c7b0990  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-a6b283b   2328Gi   RWO           Delete         Available              localblock             14m

   Copy to Clipboard Toggle word wrap

5. Check for the new StorageClass that is now present when the LocalVolume CR is created. This StorageClass is used to provide the StorageCluster PVCs in the following steps.

   $ oc get sc | grep localblock

   Copy to Clipboard Toggle word wrap

   Example output:

   NAME            PROVISIONER                    RECLAIMPOLICY
   VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION     AGE
   localblock      kubernetes.io/no-provisioner   Delete
   WaitForFirstConsumer  false                15m

   Copy to Clipboard Toggle word wrap

6. Create the StorageCluster CR that uses the localblock StorageClass to consume the PVs created by the Local Storage Operator.

   Example of StorageCluster CR ocs-cluster-service.yaml using monDataDirHostPath and localblock StorageClass.

   apiVersion: ocs.openshift.io/v1
   kind: StorageCluster
   metadata:
     name: ocs-storagecluster
     namespace: openshift-storage
   spec:
     manageNodes: false
     resources:
       mds:
         limits:
           cpu: 3
           memory: 8Gi
         requests:
           cpu: 1
           memory: 8Gi
     monDataDirHostPath: /var/lib/rook
     storageDeviceSets:
       - count: 2
         dataPVCTemplate:
           spec:
             accessModes:
               - ReadWriteOnce
             resources:
               requests:
                 storage: 2328Gi
             storageClassName: localblock
             volumeMode: Block
         name: ocs-deviceset
         placement: {}
         portable: false
         replica: 3
         resources:
           limits:
             cpu: 2
             memory: 5Gi
           requests:
             cpu: 1
             memory: 5Gi

   Copy to Clipboard Toggle word wrap
   Important

   To ensure that the OSDs have a guaranteed size across the nodes, the storage size for storageDeviceSets must be specified as less than or equal to the size of the PVs created on the nodes.

7. Create StorageCluster CR.

   $ oc create -f ocs-cluster-service.yaml

   Copy to Clipboard Toggle word wrap

   Example output

   storagecluster.ocs.openshift.io/ocs-cluster-service created

   Copy to Clipboard Toggle word wrap

Procedure

1. Click Workloads → Pods from the left pane of the OpenShift Web Console.

2. Select openshift-storage from the Project drop down list.

   For more information on the expected number of pods for each component and how it varies depending on the number of nodes, see Table 3.1, “Pods corresponding to OpenShift Container storage cluster”.

3. Verify that the following pods are in running and completed state by clicking on the Running and the Completed tabs:

   Expand

   Table 3.1. Pods corresponding to OpenShift Container storage cluster

   Component	Corresponding pods
   OpenShift Container Storage Operator	ocs-operator-* (1 pod on any worker node) ocs-metrics-exporter-*
   Rook-ceph Operator	rook-ceph-operator-* (1 pod on any worker node)
   Multicloud Object Gateway	noobaa-operator-* (1 pod on any worker node) noobaa-core-* (1 pod on any storage node) noobaa-db-* (1 pod on any storage node) noobaa-endpoint-* (1 pod on any storage node)
   MON	rook-ceph-mon-* (3 pods distributed across storage nodes)
   MGR	rook-ceph-mgr-* (1 pod on any storage node)
   MDS	rook-ceph-mds-ocs-storagecluster-cephfilesystem-* (2 pods distributed across storage nodes)
   CSI	cephfs csi-cephfsplugin-* (1 pod on each worker node) csi-cephfsplugin-provisioner-* (2 pods distributed across worker nodes) rbd csi-rbdplugin-* (1 pod on each worker node) csi-rbdplugin-provisioner-* (2 pods distributed across worker nodes)
   rook-ceph-crashcollector	rook-ceph-crashcollector-* (1 pod on each storage node)
   OSD	rook-ceph-osd-* (1 pod for each device) rook-ceph-osd-prepare-ocs-deviceset-* (1 pod for each device)

   Show more

1. Delete the volume snapshots that are using OpenShift Container Storage.

   1. List the volume snapshots from all the namespaces.

      $ oc get volumesnapshot --all-namespaces

      Copy to Clipboard Toggle word wrap

   2. From the output of the previous command, identify and delete the volume snapshots that are using OpenShift Container Storage.

      $ oc delete volumesnapshot <VOLUME-SNAPSHOT-NAME> -n <NAMESPACE>

      Copy to Clipboard Toggle word wrap

2. Delete PVCs and OBCs that are using OpenShift Container Storage.

   In the default uninstall mode (graceful), the uninstaller waits till all the PVCs and OBCs that use OpenShift Container Storage are deleted.

   If you wish to delete the Storage Cluster without deleting the PVCs beforehand, you may set the uninstall mode annotation to "forced" and skip this step. Doing so will result in orphan PVCs and OBCs in the system.

   1. Delete OpenShift Container Platform monitoring stack PVCs using OpenShift Container Storage.

      See Section 4.2, “Removing monitoring stack from OpenShift Container Storage”

   2. Delete OpenShift Container Platform Registry PVCs using OpenShift Container Storage.

      See Section 4.3, “Removing OpenShift Container Platform registry from OpenShift Container Storage”

   3. Delete OpenShift Container Platform logging PVCs using OpenShift Container Storage.

      See Section 4.4, “Removing the cluster logging operator from OpenShift Container Storage”

   4. Delete other PVCs and OBCs provisioned using OpenShift Container Storage.

      • Given below is a sample script to identify the PVCs and OBCs provisioned using OpenShift Container Storage. The script ignores the PVCs that are used internally by Openshift Container Storage.

        #!/bin/bash
        
        RBD_PROVISIONER="openshift-storage.rbd.csi.ceph.com"
        CEPHFS_PROVISIONER="openshift-storage.cephfs.csi.ceph.com"
        NOOBAA_PROVISIONER="openshift-storage.noobaa.io/obc"
        RGW_PROVISIONER="openshift-storage.ceph.rook.io/bucket"
        
        NOOBAA_DB_PVC="noobaa-db"
        NOOBAA_BACKINGSTORE_PVC="noobaa-default-backing-store-noobaa-pvc"
        
        # Find all the OCS StorageClasses
        OCS_STORAGECLASSES=$(oc get storageclasses | grep -e "$RBD_PROVISIONER" -e "$CEPHFS_PROVISIONER" -e "$NOOBAA_PROVISIONER" -e "$RGW_PROVISIONER" | awk '{print $1}')
        
        # List PVCs in each of the StorageClasses
        for SC in $OCS_STORAGECLASSES
        do
                echo "======================================================================"
                echo "$SC StorageClass PVCs and OBCs"
                echo "======================================================================"
                oc get pvc  --all-namespaces --no-headers 2>/dev/null | grep $SC | grep -v -e "$NOOBAA_DB_PVC" -e "$NOOBAA_BACKINGSTORE_PVC"
                oc get obc  --all-namespaces --no-headers 2>/dev/null | grep $SC
                echo
        done

        Copy to Clipboard Toggle word wrap
        Note

        Omit RGW_PROVISIONER for cloud platforms.

      • Delete the OBCs.

        $ oc delete obc <obc name> -n <project name>

        Copy to Clipboard Toggle word wrap

      • Delete the PVCs.

        $ oc delete pvc <pvc name> -n <project-name>

        Copy to Clipboard Toggle word wrap
        Note

        Ensure that you have removed any custom backing stores, bucket classes, etc., created in the cluster.

3. Delete the Storage Cluster object and wait for the removal of the associated resources.

   $ oc delete -n openshift-storage storagecluster --all --wait=true

   Copy to Clipboard Toggle word wrap

4. Check for cleanup pods if the uninstall.ocs.openshift.io/cleanup-policy was set to delete(default) and ensure that their status is Completed.

   $ oc get pods -n openshift-storage | grep -i cleanup
   NAME                                READY   STATUS      RESTARTS   AGE
   cluster-cleanup-job-<xx>        	0/1     Completed   0          8m35s
   cluster-cleanup-job-<yy>     		0/1     Completed   0          8m35s
   cluster-cleanup-job-<zz>     		0/1     Completed   0          8m35s

   Copy to Clipboard Toggle word wrap

5. Confirm that the directory /var/lib/rook is now empty. This directory will be empty only if the uninstall.ocs.openshift.io/cleanup-policy annotation was set to delete(default).

   $ for i in $(oc get node -l cluster.ocs.openshift.io/openshift-storage= -o jsonpath='{ .items[*].metadata.name }'); do oc debug node/${i} -- chroot /host  ls -l /var/lib/rook; done

   Copy to Clipboard Toggle word wrap

6. If encryption was enabled at the time of install, remove dm-crypt managed device-mapper mapping from OSD devices on all the OpenShift Container Storage nodes.

   1. Create a debug pod and chroot to the host on the storage node.

      $ oc debug node/<node name>
      $ chroot /host

      Copy to Clipboard Toggle word wrap

   2. Get Device names and make note of the OpenShift Container Storage devices.

      $ dmsetup ls
      ocs-deviceset-0-data-0-57snx-block-dmcrypt (253:1)

      Copy to Clipboard Toggle word wrap

   3. Remove the mapped device.

      $ cryptsetup luksClose --debug --verbose ocs-deviceset-0-data-0-57snx-block-dmcrypt

      Copy to Clipboard Toggle word wrap

      If the above command gets stuck due to insufficient privileges, run the following commands:

      • Press CTRL+Z to exit the above command.

      • Find PID of the cryptsetup process which was stuck.

        $ ps

        Copy to Clipboard Toggle word wrap

        Example output:

        PID     TTY    TIME     CMD
        778825   ?     00:00:00 cryptsetup

        Copy to Clipboard Toggle word wrap

        Take a note of the PID number to kill. In this example, PID is 778825.

      • Terminate the process using kill command.

        $ kill -9 <PID>

        Copy to Clipboard Toggle word wrap

      • Verify that the device name is removed.

        $ dmsetup ls

        Copy to Clipboard Toggle word wrap

7. Delete the namespace and wait till the deletion is complete. You will need to switch to another project if openshift-storage is the active project.

   For example:

   $ oc project default
   $ oc delete project openshift-storage --wait=true --timeout=5m

   Copy to Clipboard Toggle word wrap

   The project is deleted if the following command returns a NotFound error.

   $ oc get project openshift-storage

   Copy to Clipboard Toggle word wrap
   Note

   While uninstalling OpenShift Container Storage, if namespace is not deleted completely and remains in Terminating state, perform the steps in Troubleshooting and deleting remaining resources during Uninstall to identify objects that are blocking the namespace from being terminated.

8. Delete local storage operator configurations if you have deployed OpenShift Container Storage using local storage devices. See Removing local storage operator configurations.

9. Unlabel the storage nodes.

   $ oc label nodes  --all cluster.ocs.openshift.io/openshift-storage-
   $ oc label nodes  --all topology.rook.io/rack-

   Copy to Clipboard Toggle word wrap

10. Remove the OpenShift Container Storage taint if the nodes were tainted.

    $ oc adm taint nodes --all node.ocs.openshift.io/storage-

    Copy to Clipboard Toggle word wrap

11. Confirm all PVs provisioned using OpenShift Container Storage are deleted. If there is any PV left in the Released state, delete it.

    $ oc get pv
    $ oc delete pv <pv name>

    Copy to Clipboard Toggle word wrap

12. Delete the Multicloud Object Gateway storageclass.

    $ oc delete storageclass openshift-storage.noobaa.io --wait=true --timeout=5m

    Copy to Clipboard Toggle word wrap

13. Remove CustomResourceDefinitions.

    $ oc delete crd backingstores.noobaa.io bucketclasses.noobaa.io cephblockpools.ceph.rook.io cephclusters.ceph.rook.io cephfilesystems.ceph.rook.io cephnfses.ceph.rook.io cephobjectstores.ceph.rook.io cephobjectstoreusers.ceph.rook.io noobaas.noobaa.io ocsinitializations.ocs.openshift.io storageclusters.ocs.openshift.io cephclients.ceph.rook.io cephobjectrealms.ceph.rook.io cephobjectzonegroups.ceph.rook.io cephobjectzones.ceph.rook.io cephrbdmirrors.ceph.rook.io --wait=true --timeout=5m

    Copy to Clipboard Toggle word wrap

14. To ensure that OpenShift Container Storage is uninstalled completely, on the OpenShift Container Platform Web Console,

    1. Click Home → Overview to access the dashboard.
    2. Verify that the Persistent Storage and Object Service tabs no longer appear next to the Cluster tab.

Procedure

1. List the pods and PVCs that are currently running in the openshift-monitoring namespace.

   $ oc get pod,pvc -n openshift-monitoring
   NAME                           READY   STATUS    RESTARTS   AGE
   pod/alertmanager-main-0         3/3     Running   0          8d
   pod/alertmanager-main-1         3/3     Running   0          8d
   pod/alertmanager-main-2         3/3     Running   0          8d
   pod/cluster-monitoring-
   operator-84457656d-pkrxm        1/1     Running   0          8d
   pod/grafana-79ccf6689f-2ll28    2/2     Running   0          8d
   pod/kube-state-metrics-
   7d86fb966-rvd9w                 3/3     Running   0          8d
   pod/node-exporter-25894         2/2     Running   0          8d
   pod/node-exporter-4dsd7         2/2     Running   0          8d
   pod/node-exporter-6p4zc         2/2     Running   0          8d
   pod/node-exporter-jbjvg         2/2     Running   0          8d
   pod/node-exporter-jj4t5         2/2     Running   0          6d18h
   pod/node-exporter-k856s         2/2     Running   0          6d18h
   pod/node-exporter-rf8gn         2/2     Running   0          8d
   pod/node-exporter-rmb5m         2/2     Running   0          6d18h
   pod/node-exporter-zj7kx         2/2     Running   0          8d
   pod/openshift-state-metrics-
   59dbd4f654-4clng                3/3     Running   0          8d
   pod/prometheus-adapter-
   5df5865596-k8dzn                1/1     Running   0          7d23h
   pod/prometheus-adapter-
   5df5865596-n2gj9                1/1     Running   0          7d23h
   pod/prometheus-k8s-0            6/6     Running   1          8d
   pod/prometheus-k8s-1            6/6     Running   1          8d
   pod/prometheus-operator-
   55cfb858c9-c4zd9                1/1     Running   0          6d21h
   pod/telemeter-client-
   78fc8fc97d-2rgfp                3/3     Running   0          8d
   
   NAME                                                              STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                  AGE
   persistentvolumeclaim/my-alertmanager-claim-alertmanager-main-0   Bound    pvc-0d519c4f-15a5-11ea-baa0-026d231574aa   40Gi       RWO            ocs-storagecluster-ceph-rbd   8d
   persistentvolumeclaim/my-alertmanager-claim-alertmanager-main-1   Bound    pvc-0d5a9825-15a5-11ea-baa0-026d231574aa   40Gi       RWO            ocs-storagecluster-ceph-rbd   8d
   persistentvolumeclaim/my-alertmanager-claim-alertmanager-main-2   Bound    pvc-0d6413dc-15a5-11ea-baa0-026d231574aa   40Gi       RWO            ocs-storagecluster-ceph-rbd   8d
   persistentvolumeclaim/my-prometheus-claim-prometheus-k8s-0        Bound    pvc-0b7c19b0-15a5-11ea-baa0-026d231574aa   40Gi       RWO            ocs-storagecluster-ceph-rbd   8d
   persistentvolumeclaim/my-prometheus-claim-prometheus-k8s-1        Bound    pvc-0b8aed3f-15a5-11ea-baa0-026d231574aa   40Gi       RWO            ocs-storagecluster-ceph-rbd   8d

   Copy to Clipboard Toggle word wrap

2. Edit the monitoring configmap.

   $ oc -n openshift-monitoring edit configmap cluster-monitoring-config

   Copy to Clipboard Toggle word wrap

3. Remove any config sections that reference the OpenShift Container Storage storage classes as shown in the following example and save it.

   Before editing

   Expand

   . . . apiVersion: v1 data: config.yaml: | alertmanagerMain: volumeClaimTemplate: metadata: name: my-alertmanager-claim spec: resources: requests: storage: 40Gi storageClassName: ocs-storagecluster-ceph-rbd prometheusK8s: volumeClaimTemplate: metadata: name: my-prometheus-claim spec: resources: requests: storage: 40Gi storageClassName: ocs-storagecluster-ceph-rbd kind: ConfigMap metadata: creationTimestamp: "2019-12-02T07:47:29Z" name: cluster-monitoring-config namespace: openshift-monitoring resourceVersion: "22110" selfLink: /api/v1/namespaces/openshift-monitoring/configmaps/cluster-monitoring-config uid: fd6d988b-14d7-11ea-84ff-066035b9efa8 . . . Copy to Clipboard Toggle word wrap

   Show more

   After editing

   Expand

   . . . apiVersion: v1 data: config.yaml: | kind: ConfigMap metadata: creationTimestamp: "2019-11-21T13:07:05Z" name: cluster-monitoring-config namespace: openshift-monitoring resourceVersion: "404352" selfLink: /api/v1/namespaces/openshift-monitoring/configmaps/cluster-monitoring-config uid: d12c796a-0c5f-11ea-9832-063cd735b81c . . . Copy to Clipboard Toggle word wrap

   Show more

   In this example, alertmanagerMain and prometheusK8s monitoring components are using the OpenShift Container Storage PVCs.

4. Delete relevant PVCs. Make sure you delete all the PVCs that are consuming the storage classes.

   $ oc delete -n openshift-monitoring pvc <pvc-name> --wait=true --timeout=5m

   Copy to Clipboard Toggle word wrap

Procedure

1. Edit the configs.imageregistry.operator.openshift.io object and remove the content in the storage section.

   $ oc edit configs.imageregistry.operator.openshift.io

   Copy to Clipboard Toggle word wrap
   Expand

   Before editing

   . . . storage: pvc: claim: registry-cephfs-rwx-pvc . . . Copy to Clipboard Toggle word wrap

   After editing

   . . . storage: . . . Copy to Clipboard Toggle word wrap

   Show more

   In this example, the PVC is called registry-cephfs-rwx-pvc, which is now safe to delete.

2. Delete the PVC.

   $ oc delete pvc <pvc-name> -n openshift-image-registry --wait=true --timeout=5m

   Copy to Clipboard Toggle word wrap

Procedure

1. Remove the ClusterLogging instance in the namespace.

   $ oc delete clusterlogging instance -n openshift-logging --wait=true --timeout=5m

   Copy to Clipboard Toggle word wrap

   The PVCs in the openshift-logging namespace are now safe to delete.

2. Delete PVCs.

   $ oc delete pvc <pvc-name> -n openshift-logging --wait=true --timeout=5m

   Copy to Clipboard Toggle word wrap