Merge branch 'main' into pvt/ghissue-1518-iscsi

content/docs/deployment/helm/modules/installation/replication/installation.md

@@ -29,6 +29,18 @@ Please follow the steps [here](../install-repctl) to install & configure Dell Re
 #### Using the installation script
 Please follow the steps [here](../install-script) to install & configure Dell Replication Controller using script.
 
+#### _(Optional)_ FQDN Setup
+If CSM Replication is being deployed using two clusters in an environment where the DNS is not configured, and the cluster API endpoints are FQDNs, it is necessary to add the `<FQDN>:<IP>` mapping in the /etc/hosts file in order to resolve queries to the remote API server.
+This change will need to be made to the /etc/hosts file on:
+- The environment that is performing the installation/management (wherever `repctl` or the install script is used).
+- Both dell-replication-controller-manager deployments.
+    - To update the dell-replication-controller-manager deployment, execute the command below, replacing the fields for the remote cluster's FQDN and IP. Make sure to update the deployment on both the primary and disaster recovery clusters.
+
+      ```bash
+      kubectl patch deployment -n dell-replication-controller dell-replication-controller-manager \
+      -p '{"spec":{"template":{"spec":{"hostAliases":[{"hostnames":["<remote-FQDN>"],"ip":"<remote-IP>"}]}}}}'
+      ```
+
 ### Install CSI driver
 The following CSI drivers support replication:
 1. CSI driver for PowerMax

content/docs/replication/_index.md

@@ -34,6 +34,8 @@ CSM for Replication provides the following capabilities:
 
 > _**NOTE**_: To add or delete volumes to the existing SYNC Replication Group in PowerStore, the user needs to pause and then resume the replication group. For more details, please refer to the troubleshooting section.
 
+> _**NOTE**_: To delete last volume of the existing SYNC Replication Group in PowerStore, the user needs to first unassign the replication policy from the existing SYNC Replication Group. For more details, please refer to the troubleshooting section.
+
 ## Details
 
 As on the storage arrays, all replication related Kubernetes entities are required/created in pairs -

content/docs/replication/troubleshooting.md

@@ -17,3 +17,4 @@ description: >
 | PV and/or PVCs are not being created at the source/target cluster. If you check the controller's logs you can see `no such host` errors| Make sure cluster-1's API is pingable from cluster-2 and vice versa. If one of your clusters is OpenShift located in a private network and needs records in /etc/hosts, `exec` into controller pod and modify `/etc/hosts` manually. |
 | After upgrading to Replication v1.4.0, if `kubectl get rg` returns an error `Unable to list "replication.storage.dell.com/v1alpha1, Resource=dellcsireplicationgroups"`| This means `kubectl` still doesn't recognize the new version of CRD `dellcsireplicationgroups.replication.storage.dell.com` after upgrade. Running the command `kubectl get DellCSIReplicationGroup.v1.replication.storage.dell.com/<rg-id> -o yaml` will resolve the issue. |
 | To add or delete volumes in the existing SYNC Replication Group in PowerStore, you may encounter the error `The operation is restricted as sync replication session for resource <Replication Group Name> is not paused` | To resolve this, you need to pause the replication group, add the volume, and then resume the replication group (RG). The commands for the pause and resume operations are: `repctl --rg <rg-id> exec -a suspend`  `repctl --rg <rg-id> exec -a resume` |
+| To delete the last volume from the existing SYNC Replication Group in Powerstore, you may encounter the error 'failed to remove volume from volume group: The operation cannot be completed on metro or replicated volume group because volume group will become empty after last members are removed' | To resolve this unmap the volume group from protection policy which will delete the replication session. After that, you can successfully delete the last volume in that SYNC Replication group.|