Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE]: CSI Powermax - Volumes Not Deleted on Target Array #801

Closed
delldubey opened this issue May 8, 2023 · 1 comment
Closed

[FEATURE]: CSI Powermax - Volumes Not Deleted on Target Array #801

delldubey opened this issue May 8, 2023 · 1 comment
Assignees
Labels
area/csi-powermax Issue pertains to the CSI Driver for Dell EMC PowerMax area/csm-replication Issue pertains to the CSM Replication module type/feature A feature. This label is applied to a feature issues.
Milestone

Comments

@delldubey
Copy link
Contributor

Bug Description

When deleting source-side block-type PVC/PV after usage, the corresponding PowerMax Volume on the source side array is deleted. However, the target-side Volume remains on the storage array even after its associated PV is deleted from Kubernetes. This artifact should be deleted on both arrays, not just the source side array.

Logs

Logs for target-side driver do not indicate delete volume methods are being called. Source-side driver does include calls to delete the volume.

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

  1. Provision a replicated volume with appropriate Storage Class fields set to Delete (Remote PV, retention policy, etc).
  2. Delete the source-side PVC.
  3. Source side Volume will be deleted from storage array.
  4. Target side Volume will not be deleted from storage array.

Expected Behavior

Target side volume should be deleted from storage array alongside its source-side equivalent.

CSM Driver(s)

CSI PowerMax v2.6

Installation Type

Helm v3

Container Storage Modules Enabled

Replication v1.6

Container Orchestrator

Kubernetes 1.26

Operating System

RHEL 8.4

@delldubey delldubey added needs-triage Issue requires triage. type/feature-request New feature request. This is the default label associated with a feature request issue. labels May 8, 2023
@delldubey delldubey added this to the v1.7.0 milestone May 8, 2023
@delldubey delldubey self-assigned this May 8, 2023
@delldubey delldubey added area/csm-replication Issue pertains to the CSM Replication module area/csi-powermax Issue pertains to the CSI Driver for Dell EMC PowerMax labels May 8, 2023
@csmbot
Copy link
Collaborator

csmbot commented May 8, 2023

@delldubey: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and assign an appropriate priority label.


We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at container.storage.modules@dell.com.

@shanmydell shanmydell added type/feature A feature. This label is applied to a feature issues. and removed needs-triage Issue requires triage. type/feature-request New feature request. This is the default label associated with a feature request issue. labels May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/csi-powermax Issue pertains to the CSI Driver for Dell EMC PowerMax area/csm-replication Issue pertains to the CSM Replication module type/feature A feature. This label is applied to a feature issues.
Projects
None yet
Development

No branches or pull requests

3 participants