Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell Container Storage Modules (CSM) Family for Replication PowerScale: Replication Artifacts Remain After Deletion

Summary: Replicated Persistent Volumes (PVs) and DellCSIReplicationGroups (RGs) occasionally do not get deleted when issued relevant Kubernetes deletion commands. SyncIQ policies on PowerScale arrays can also improperly persist after their related RG is deleted. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

When Kubernetes objects (Persistent Volumes (PVs) or DellCSIReplicationGroups (RGs) are issued delete commands, the kubectl command may stop responding indefinitely instead of deleting the PV or RG in question. When the RGs are successfully deleted, their associated SyncIQ policies on related PowerScale storage arrays may not be deleted as intended. 

This can create issues when further replication is attempted with the same Kubernetes storage class. This issue can cause scenarios where storage space is not freed up after it is no longer necessary.

Issue is reported here: https://github.com/dell/csm/issues/523

Cause

Finalizer tags in the CSM-managed Kubernetes objects do not properly honor and address Container Storage Modules (CSM) replication when the object is deleted. This results in the object remaining in a "Terminating" state indefinitely because the conditions in its finalizer are not met.
 
SyncIQ policy deletion is not properly performed when CSM replication controller and replication sidecar handle the deletion of an RG. This results in the SyncIQ policy remaining on the storage array even after its RG is deleted.

Resolution

Resolution:

Engineering has resolved this issue in Dell CSM for PowerScale 1.6.0.
Workaround:
For Kubernetes objects:
  1. Cancel the deletion that is not responding (for example, Ctrl+C). Manually access the objects that are failing to delete with the following command:
  • For RGs:
kubectl edit rg <RG NAME>
  • For PVs:
kubectl edit pv <PV NAME>
  1. This opens the relevant object in a text editor. Inside the object, there are several categories of tags, as seen below:
Object Tags
  1. Manually delete the "finalizers:" line and its entries. In the above case, this is:

Finalizer Lines to Delete

 

  1. Save the file in the text editor, exit the editor, and then run the deletion command again. This process may be repeated for all replicated PVs and RGs that are failing to delete.


For deleting SyncIQ policies left on the array:

  1. Log in to the source PowerScale array using its web user interface.
  2. Go to the Data Protection tab and select SyncIQ.
  3. From the SyncIQ page, go to the Policies subtab.
  4. On the policy that must be deleted, click Actions, and then Delete Policy.
  5. Repeat for the target and destination PowerScale array as needed.

Affected Products

Container Storage Modules

Products

Container Storage Modules Family
Article Properties
Article Number: 000206294
Article Type: Solution
Last Modified: 03 Jul 2023
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.