Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1704888

Summary: delete the snapshots and volume at the end of uss.t
Product: [Community] GlusterFS Reporter: Raghavendra Bhat <rabhat>
Component: testsAssignee: Raghavendra Bhat <rabhat>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: urgent    
Version: mainlineCC: atumball, bugs
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-7.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-05 07:51:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.