Bug 1626543 - dht/tests: Create a .t to test all possible combinations for file rename
Summary: dht/tests: Create a .t to test all possible combinations for file rename
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
Assignee: Nithya Balachandran
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-07 15:15 UTC by Nithya Balachandran
Modified: 2019-08-19 07:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 07:28:48 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 21121 0 None Merged tests/dht: Add a test file for file renames 2019-08-19 07:28:47 UTC

Description Nithya Balachandran 2018-09-07 15:15:43 UTC 
Description of problem:
dht file renames can follow different code paths depending on the values of the hashed and cached subvols for the src and target. We need a test to validate all combinations.


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 2018-09-07 15:20:50 UTC 
REVIEW: https://review.gluster.org/21121 (tests/dht: Add a test file for file renames) posted (#1) for review on master by N Balachandran
Comment 2 Worker Ant 2019-08-19 07:28:48 UTC 
REVIEW: https://review.gluster.org/21121 (tests/dht: Add a test file for file renames) merged (#6) on master by N Balachandran
Note You need to log in before you can comment on or make changes to this bug.