Skip to content

Spectrum Scale Fileset not getting deleted after PVC deletion for clone PVCs(non bound) #516

Open
@vrushch

Description

@vrushch

Describe the bug

Created 50 pvcs and 2500 clones of those pvcs. Some cloned pvcs were not in bound state due to mmxcp issue. Then deleted all pvcs including clone one which were not in bound state. All pv,pvc got deleted, but spectrum scale filesets are still not deleted

To Reproduce
Steps to reproduce the behavior:

  1. Create PVC
  2. Create multiple clone copies of above pvc
  3. Before clone pvc get into bound state, delete all pvc
  4. Fileset not getting deleted

Expected behavior
Spectrum Scale filesets should be deleted for all the deleted pvc.

Environment
Please run the following an paste your output here:

# Deployment
[root@remote-csi-master functional-tests]# kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:38:50Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:32:41Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}
[root@remote-csi-master functional-tests]#

[root@remote-csi-scalegui ~]# rpm -qa | grep gpfs
gpfs.msg.en_US-5.1.2-0.noarch
gpfs.gpl-5.1.2-0.noarch
gpfs.java-5.1.2-0.x86_64
gpfs.docs-5.1.2-0.noarch
gpfs.base-5.1.2-0.x86_64
gpfs.license.adv-5.1.2-0.x86_64
gpfs.compression-5.1.2-0.x86_64
gpfs.afm.cos-1.0.0-3.x86_64
gpfs.gss.pmsensors-5.1.2-0.el7.x86_64
gpfs.gui-5.1.2-0.noarch
gpfs.librdkafka-5.1.2-0.el7.x86_64
gpfs.gskit-8.0.55-19.x86_64
gpfs.adv-5.1.2-0.x86_64
gpfs.crypto-5.1.2-0.x86_64
gpfs.gss.pmcollector-5.1.2-0.el7.x86_64
[root@remote-csi-scalegui ~]#

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Images used : dev-2.4.0

Metadata

Metadata

Assignees

Labels

Customer Impact: Localized high impact(3) Reduction of function. Significant impact to workload.Customer Probability: Medium(3) Issue occurs in normal path but specific limited timing window, or other mitigating factorSeverity: 2Indicates that the issue is critical and must be addressed before milestone.Type: BugIndicates issue is an undesired behavior, usually caused by code error.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions