Bug 1825892 - StorageClasses and PVs are not cleaned completely after running the csi verification tool
Summary: StorageClasses and PVs are not cleaned completely after running the csi verif...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.7.0
Assignee: Christian Huffman
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-20 12:53 UTC by Qin Ping
Modified: 2021-02-24 15:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:12:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:13:33 UTC

Description Qin Ping 2020-04-20 12:53:53 UTC
Description of problem:
StorageClasses and PVs are not cleaned completely after running the csi verification tool 

Version-Release number of selected component (if applicable):
Test cluster: 4.4.0-0.nightly-2020-04-18-095545


How reproducible:
often

Steps to Reproduce:
1. setup an OCP cluster
2. install OCS4.3 from operator hub
3. install ember csi from operator hub
4. run csi verification test.

Actual results:
After test there are some storageclasses and PVs are not cleaned.
piqin@Worker testdata]$ oc get sc|grep e2e
my-ceph.ember-csi.io-e2e-volume-927-xk74d    my-ceph.ember-csi.io                    Delete          Immediate              true                   150m
my-ceph.ember-csi.io-e2e-volume-9558-4w2g7   my-ceph.ember-csi.io                    Delete          Immediate              true                   174m
[piqin@Worker testdata]$ oc get ns|grep e2e
[piqin@Worker testdata]$ oc get pv|grep e2e
pvc-2848d5fd-be55-4c5d-99ed-b2f301b46223   1Gi        RWO            Delete           Released   e2e-volume-927/my-ceph.ember-csi.iocfpkr    my-ceph.ember-csi.io-e2e-volume-927-xk74d             150m
pvc-fe06d841-390e-4681-845b-843fd166116e   1Gi        RWO            Delete           Released   e2e-volume-9558/my-ceph.ember-csi.iothk6k   my-ceph.ember-csi.io-e2e-volume-9558-4w2g7            174m


Expected results:
All the resources created by csi verification tool are cleaned.

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 8 Qin Ping 2020-08-26 06:20:04 UTC
Hello,

Ran csi verification testing on an OCP 4.6 cluster(Cluster version: 4.6.0-0.nightly-2020-08-25-222652) 3 times with the following config:
ShortName: ebs
StorageClass:
  FromFile: storageclass.yaml
SnapshotClass:
  FromName: true
DriverInfo:
  Name: ebs.csi.aws.com
  SupportedSizeRange:
    Min: 1Gi
    Max: 16Ti
  SupportedFsType:
    xfs: {}
    ext4: {}
  SupportedMountOption:
    dirsync: {}
  TopologyKeys: ["topology.ebs.csi.aws.com/zone"]
  Capabilities:
    persistence: true
    fsGroup: true
    block: true
    exec: true
    snapshotDataSource: true #snapshot
    pvcDataSource: false #clone
    multipods: true
    singleNodeVolume: true
    volumeLimits: false
    controllerExpansion: true
    nodeExpansion: true
    RWX: false
    topology: true


All 3 tests were passed and no instances created by e2e testing were left, so I think we can mark this bug as verified.
54 pass, 124 skip (6m56s)
$ oc get volumeattachments,ns,sc,volumesnapshots,volumesnapshotcontents,volumesnapshotclasses,pv,pvc -A|grep e2e

Comment 9 Christian Huffman 2020-08-26 13:48:18 UTC
I'm marking this as VERIFIED per the previous comment.

Comment 12 errata-xmlrpc 2021-02-24 15:12:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:5633


Note You need to log in before you can comment on or make changes to this bug.