Bug 1704888 - delete the snapshots and volume at the end of uss.t
Summary: delete the snapshots and volume at the end of uss.t
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
Assignee: Raghavendra Bhat
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-30 18:05 UTC by Raghavendra Bhat
Modified: 2019-07-05 07:51 UTC (History)
2 users (show)

Fixed In Version: glusterfs-7.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-05 07:51:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22649 0 None Merged tests: delete the snapshots and the volume after the tests 2019-05-06 13:59:12 UTC

Description Raghavendra Bhat 2019-04-30 18:05:40 UTC
Description of problem:

The current uss.t test in the test infrastructure from the glusterfs codebase performs multiple tests and at the end leaves the volume(s) and snap(s) to be cleaned up by the cleanup () function.

While this is functionaly correct, it might take more time and effort for cleanup function to release all the resources (in a hard way). So, delete all the snapshots and the volume after the tests.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-04-30 18:13:28 UTC
REVIEW: https://review.gluster.org/22649 (tests: delete the snapshots and the volume after the tests) posted (#2) for review on master by Raghavendra Bhat

Comment 2 Worker Ant 2019-05-06 13:59:13 UTC
REVIEW: https://review.gluster.org/22649 (tests: delete the snapshots and the volume after the tests) merged (#4) on master by Amar Tumballi

Comment 3 Amar Tumballi 2019-07-05 07:51:28 UTC
I noticed that after the patch got merged, no more issues seen with the particular test. Looks like it was enough.


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