summaryrefslogtreecommitdiffstats
path: root/tests/functional/dht
Commit message (Collapse)AuthorAgeFilesLines
* [Test] Add file rename test when dest exist in diff subvol combinationsPranav2020-07-081-0/+919
| | | | | | | | Tests to validate the behaviour of rename cases when destination file exists and is hashed or cached to different subvol combinations Change-Id: I44752a444d9c112d590efd66c48ff095c22fcecd Signed-off-by: Pranav <prprakas@redhat.com>
* [Test] Add file rename tests when dest file in src hashed/cached subvolPranav2020-06-251-0/+639
| | | | | | | | | Tests to validate behaviour of different scenarios of file rename cases, when destination file exists intially and is hashed to the source file hashed or cached subvol. Change-Id: Iec12d33c459cb966861d2efac2bae85103555cc1 Signed-off-by: Pranav <prprakas@redhat.com>
* [TestFix] Change method namesayaleeraut2020-06-241-1/+1
| | | | | | | | Changing the method name from test_readdirp_with_rebalance(self) to test_access_file_with_stale_linkto_xattr(self) Change-Id: I5503e301d65f96e38aa135827d8bc698a0371281 Signed-off-by: sayaleeraut <saraut@redhat.com>
* [Test] Check access file with stale linkto xattrsayaleeraut2020-06-241-0/+169
| | | | | | | | | | | | | | | | | | | | Description: The test script verfies that a file with stale linkto xattr can be accessed from a non-root user. Steps: 1) Create a volume and start it. 2) Mount the volume on client node using FUSE. 3) Create a file. 4) Enable performance.parallel-readdir and performance.readdir-ahead on the volume. 5) Rename the file in order to create a linkto file. 6) Force the linkto xattr values to become stale by changing the dht subvols in the graph. 7) Login as an non-root user and access the file. Change-Id: I4f275dedd47a851c2c4839f51cf1867638a66667 Signed-off-by: sayaleeraut <saraut@redhat.com>
* [TestFix] Remove tier related kwarg from testBala Konda Reddy M2020-06-241-1/+1
| | | | | | | | | Removing 'add_to_hot_tier' parameter as it defaults to False and it is not needed for the add-brick operation in the test as the volume type is not tier. Change-Id: I4a697a453e368197dfaf143d344a623d449e2614 Signed-off-by: Bala Konda Reddy M <bala12352@gmail.com>
* [Test] Validate delete file picked for migrationsayaleeraut2020-06-191-0/+165
| | | | | | | | | | | | | | | | | | | Description: The test script verifies that if a file is picked for migration and if it is deleted, then the file should be removed successfully. Steps : 1) First create a big data file of 10GB. 2) Rename that file, such that after rename a linkto file is created (we are doing this to make sure that file is picked for migration.) 3) Add bricks to the volume and trigger rebalance using force option. 4) When the file has been picked for migration, delete that file from the mount point. 5) Check whether the file has been deleted or not on the mount-point as well as the back-end bricks. Change-Id: I137512a1d94a89aa811a3a9d61a9fb4002bf26be Signed-off-by: sayaleeraut <saraut@redhat.com>
* [Test] Add dht file rename cases where the destination file existsPranav2020-06-191-0/+540
| | | | | | | | Tests to validate behaviour of different scenarios of file rename cases, when destination file exists intially. Change-Id: I12cd2568540bec198f1c3cf85213e0107c9ddd6b Signed-off-by: Pranav <prprakas@redhat.com>
* [Test] Add dht file rename cases where destination doesn't existPranav2020-06-151-0/+450
| | | | | | | | Tests to validate behaviour of different scenarios of file rename cases, when destination file doesn't exist intially. Change-Id: I3f22d61d9bd2fa5c54930715e2ef976c7d1ba54e Signed-off-by: Pranav <prprakas@redhat.com>
* [Test] Check stack overflow in readdirpsayaleeraut2020-06-051-0/+131
| | | | | | | | | | | | | | | | | | | Description: The TC checks that there is no stack overflow in readdirp with parallel-readdir enabled. Steps : 1) Create a volume. 2) Mount the volume using FUSE. 3) Enable performance.parallel-readdir and performance.readdir-ahead on the volume. 4) Create 10000 files on the mount point. 5) Add-brick to the volume. 6) Perform fix-layout on the volume (not rebalance). 7) From client node, rename all the files, this will result in creation of linkto files on the newly added brick. 8) Do ls -l (lookup) on the mount-point. Change-Id: I821efea55e3f8981ecd307b93781f2da5790c548 Signed-off-by: sayaleeraut <saraut@redhat.com>
* [Test] Validate file rename with brick downsayaleeraut2020-06-031-0/+172
| | | | | | | | | | | | | | | | | | | | | | | | | | Description: The TC checks that there is no data loss when rename is performed with a brick of volume down. Steps : 1) Create a volume. 2) Mount the volume using FUSE. 3) Create 1000 files on the mount point. 4) Create the soft-link for file{1..100} 5) Create the hard-link for file{101..200} 6) Check for the file count on the mount point. 7) Begin renaming the files, in multiple iterations. 8) Let few iterations of the rename complete successfully. 9) Then while rename is still in progress, kill a brick part of the volume. 10) Let the brick be down for sometime, such that the a couple of rename iterations are completed. 11) Bring the brick back online. 12) Wait for the IO to complete. 13) Check if there is any data loss. 14) Check if all the files are renamed properly. Change-Id: I7b7c4aed7df7f19a10ec8c2577dfec1f1ceeb46c Signed-off-by: sayaleeraut <saraut@redhat.com>
* [TestFix] DHT Tests - Remove NFS protocolsayaleeraut2020-05-211-10/+11
| | | | | | | | | | | | | | | Scenarios: 1 - Rename directory when destination is not present 2 - Rename directory when destination is present The TC was failing when the volume was mounted using NFS at validate_files_in_dir() because the method uses 'trusted.glusterfs.pathinfo' on the mount, which is a glusterfs specific xattr. When the volume is mounted using NFS, it cannot find the xattr and hence it failed. Change-Id: Ic61de773525e717a73178a4694c015276da2a688 Signed-off-by: sayaleeraut <saraut@redhat.com>
* [Test] test rmdir with subvol downPranav2020-05-131-0/+361
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | test case: (rmdir with subvol down) case -1: - create parent - bring down a non-hashed subvolume for directory child - create parent/child - rmdir /mnt/parent will fail with ENOTCONN case -2: - create dir1 and dir2 - bring down hashed subvol for dir1 - bring down a non-hashed subvol for dir2 - rmdir dir1 should fail with ENOTCONN - rmdir dir2 should fail with ENOTCONN case -3: - create parent - mkdir parent/child - touch parent/child/file - bringdown a subvol where file is not present - rm -rf parent - Only file should be deleted - rm -rf should fail with ENOTCONN case -4: - Bring down a non-hashed subvol for parent_dir - mkdir parent - rmdir parent should fails with ENOTCONN Change-Id: I8fbd425729aaf04eabfced315f94167178918e31 Co-authored-by: Susant Palai <spalai@redhat.com> Signed-off-by: Susant Palai <spalai@redhat.com> Signed-off-by: Pranav <prprakas@redhat.com>
* [TestFix][DHT] Moving test steps from teardown class to teardownSri Vignesh2020-05-1113-98/+98
| | | | | | | Move cases from teardown class to teardown in dht Change-Id: Id0cf120c6229715521ae19fd4bb00cad553d701f Signed-off-by: Sri Vignesh <sselvan@redhat.com>
* [Test] Add tc to check custom file xattrskshithijiyer2020-05-071-0/+256
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Description: This test case creates files at mount point and verifies custom attributes across bricks Testcase steps: 1.Create a gluster volume and start it. 2.Create file and link files. 3.Create a custom xattr for file. 4.Verify that xattr for file is displayed on mount point and bricks 5.Modify custom xattr value and verify that xattr for file is displayed on mount point and bricks 6.Verify that custom xattr is not displayed once you remove it 7.Create a custom xattr for symbolic link. 8.Verify that xattr for symbolic link is displayed on mount point and sub-volume 9.Modify custom xattr value and verify that xattr for symbolic link is displayed on mount point and bricks 10.Verify that custom xattr is not displayed once you remove it. Change-Id: Iff7360273369c77da243f2c09df2e10a0eec27ea Co-authored-by: Kartik_Burmee <kburmee@redhat.com> Signed-off-by: Kartik_Burmee <kburmee@redhat.com> Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [TestFix] Add code to override the volume configsayaleeraut2020-04-231-38/+73
| | | | | | | | | | | | | | | Changing the distribute count to 4 for the volume type distributed-replicated or distributed-dispersed, as earlier with distribute count 2, after remove-brick, the dist-rep & dist-disp volumes were converted to pure rep or pure dispersed, which caused "layout not complete" error as with the DHT pass-through feature layout is not set on bricks if volume type is pure replicated/pure dispersed on gluster version 6.0 Adding distributed-arbiter volume type and have added code to override its configuration as well. Change-Id: Ic7a3404ed49d24f956de33f7bd5ca8ea61297e5b Signed-off-by: sayaleeraut <saraut@redhat.com>
* [Test] Add tc to stop rebalance with migration in progresskshithijiyer2020-04-221-0/+167
| | | | | | | | | | | | | | | | | | | | | | Description: This test case creates a large file at mount point, adds extra brick and initiates rebalance. While migration is in progress, it stops rebalance process and checks if it has stopped. Testcase Steps: 1. Create and start a volume. 2. Mount volume on client and create a large file. 3. Add bricks to the volume and check layout 4. Rename the file such that it hashs to different subvol. 5. Start rebalance on volume. 6. Stop rebalance on volume. Change-Id: I7edd37a548467d6624ffe1efa64b0c1b56ff26ed Co-authored-by: Kartik_Burmee <kburmee@redhat.com> Signed-off-by: Kartik_Burmee <kburmee@redhat.com> Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [TestFix] Fix to make TC compatible with DHT libsayaleeraut2020-04-221-38/+52
| | | | | | | | | | | | | The TC was failing with "AssertionError: ('hash range is not there %s', False)" even though the bricks were healed and the directory was created on non-hashed bricks. This was due to the conflict between the TC and the DHT library changes (added to fix the issues caused by DHT pass-through functionality). The code is now modified according to the library changes and hence the TC works fine. Change-Id: I501e7db89643822fbc711e631ceacda79e4c4ea4 Signed-off-by: sayaleeraut <saraut@redhat.com>
* [Testfix] Fix logging errorkshithijiyer2020-04-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Problem: Line 135 is missing () which leads to the below trace back when the testcase fails: ``` Traceback (most recent call last): File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit msg = self.format(record) File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format return fmt.format(record) File "/usr/lib64/python2.7/logging/__init__.py", line 464, in format record.message = record.getMessage() File "/usr/lib64/python2.7/logging/__init__.py", line 328, in getMessage msg = msg % self.args TypeError: not all arguments converted during string formatting Logged from file test_volume_start_stop_while_rebalance_in_progress.py, line 135 ``` Solution: Adding the missing () brackets in line 135. Change-Id: I318a5b838f01840afee5d4109645cc7dcd86c8fa Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [Test]: check heal of custom xattr on newly added bricksayaleeraut2020-03-261-0/+172
| | | | | | | | | | | | | | | | BZ#1702298 - Custom xattrs are not healed on newly added brick Test Steps: 1) Create a volume. 2) Mount the volume using FUSE. 3) Create 100 directories on the mount point. 4) Set the xattr on the directories. 5) Add bricks to the volume and trigger rebalance. 6) Wait for rebalance to complete. 7) After rebalance completes,check if all the bricks have healed. 8) Check the xattr for dirs on the newly added bricks. Change-Id: If83f65ea163ccf16f9024d6b3a867ba7b35773f0 Signed-off-by: sayaleeraut <saraut@redhat.com>
* [Test+libfix] Add testcase to access of filekshithijiyer2020-03-191-0/+172
| | | | | | | | | | | | | Testcase steps: (file access) - rename the file so that the hashed and cached are different - make sure file can be accessed as long as cached is up Fixes a library issue as well in find_new_hashed() Change-Id: Id81264848d6470b9fe477b50290f5ecf917ceda3 Co-authored-by: Susant Palai <spalai@redhat.com> Signed-off-by: Susant Palai <spalai@redhat.com> Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [Test+libfix] Testcases for rename with subvol downkshithijiyer2020-03-171-0/+228
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Case 1: 1.mkdir srcdir and dstdir(such that srcdir and dstdir hashes to different subvols) 2.Bring down srcdir hashed subvol 3.mv srcdir dstdir (should fail) Case 2: 1.mkdir srcdir dstdir 2.Bring down srcdir hashed 3.Bring down dstdir hashed 4.mv srcdir dstdir (should fail) Case 3: 1.mkdir srcdir dstdir 2.Bring down dstdir hashed subvol 3.mv srcdir dstdir (should fail) Additional library fix details: Also fixing library function to work with distributed-disperse volume by removing `if oldhashed._host != brickdir._host:` as the same node can host multiple bricks of the same volume. Change-Id: Iaa472d1eb304b547bdec7a8e6b62c1df1a0ce591 Co-authored-by: Susant Palai <spalai@redhat.com> Signed-off-by: Susant Palai <spalai@redhat.com> Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [Testfix] Remove python version dependency(Part 4)kshithijiyer2020-02-2612-57/+37
| | | | | | | | | Please refer to commit message of patch [1]. [1] https://review.gluster.org/#/c/glusto-tests/+/24140/ Change-Id: I25d30f7bdb20f0825709c4c852140e1906870ce7 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [Testfix] Fix test_excerise_rebalance_command script failureskshithijiyer2020-02-251-35/+68
| | | | | | | | | | | | Script sometimes fails at expand volume with "Already part of volume" error fixed it with this patch. Change-Id: I628bbdb268e5a42112f68d9148da6bdb775acd26 Co-authored-by: Prasad Desala <tdesala@redhat.com>, Milind Waykole <milindwaykole96@gmail.com> Signed-off-by: Prasad Desala <tdesala@redhat.com> Signed-off-by: Milind Waykole <milindwaykole96@gmail.com> Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [Test] Added test case to copy directorykshithijiyer2020-01-241-0/+227
| | | | | | | | | | | Description: This test creates directories and subdirectories and their copies at mount point and checks for layout and directory information at all subvols. Change-Id: Iabce046e7ce63c5428061bcefb98d06359dac8bd Co-authored-by: Kartik_Burmee <kburmee@redhat.com> Signed-off-by: Kartik_Burmee <kburmee@redhat.com> Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [Fix] Remove variable script_local_path(Part 2)kshithijiyer2020-01-0711-33/+11
| | | | | | | | Please refer to the commit message of the below patch: https://review.gluster.org/#/c/glusto-tests/+/23902/ Change-Id: I0d2eeb978c6757d6d910ebfe21b07811bf74b80a Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* [py2to3] Add py3 support in 'tests/functional/dht'Valerii Ponomarov2019-12-1824-109/+134
| | | | | Change-Id: I44fe85519c8fd381064670e54dac8736107b0928 Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
* [DHT] : Changing the arguments passed to a function.sayaleeraut2019-12-091-2/+2
| | | | | | | | | | | | Earlier arguments passed to function log_volume_info_and_status in the code were (self.mnode, self.volume), which is incorrect. The function takes arguments as (mnode, volname). Changing the second incorrect argument self.volume to self.volname for the function log_volume_info_and_status at all its occurances in the code. Change-Id: If9bca96679f37c2d7cbcf0f34a16df8549110e21 Signed-off-by: sayaleeraut <saraut@redhat.com>
* TC: test_add_brick_while_remove_brick_is_in_progressPrasad Desala2019-10-201-1/+10
| | | | | | | | | | Add-brick command failure is leaving the directories created on the backend bricks which is resulting in the failure of the subsequent cases. Added some changes to clean the bricks. Change-Id: I108efbcaef2010f6fd52c334446059f96fff3741 Signed-off-by: Prasad Desala <tdesala@redhat.com>
* [DHT] : Modifying the messages in g.log.info and ExecutionErrorsayaleeraut2019-09-111-4/+4
| | | | | | | | | | | | The ExecutionError msg at line 66 should be "failed to clean-up volume" because it is under tearDownClass. The g.log.info msg at line 123 should be "Checking if gfid xattr of directories is displayed and is same on all the bricks on the server node" as the code below it checks for the gfid xattr on the bricks on server node and not if it is displayed on mount point. Change-Id: If4e20e3487a44c1cc7047504d19cc9859424ccd4 Signed-off-by: sayaleeraut <saraut@redhat.com>
* do getfattr in brick_path rather than m_pointyinkui2019-09-111-2/+3
| | | | | Change-Id: I240ecb0b4a9c99134b7a5cd237a59c2857d0fb7b Signed-off-by: yinkui <13965432176@163.com>
* access self.mnod so we must get layout in mount_point/dirpath, and change ↵yinkui2019-09-041-2/+2
| | | | | | | the log. Change-Id: I361b2c59108b19480906f6dfd49b023ed1eb05cd Signed-off-by: yinkui <13965432176@163.com>
* This TC is to ammend the previous TC to prevent it from failing - picking up ↵sayalee2019-05-281-7/+29
| | | | | | | random servers which are not part of volume Change-Id: I8dcb8fcd8fd0bfaefcaf24a3f2aa222b44ff7f24 Signed-off-by: sayalee <root@localhost.localdomain>
* TC: test_negative_exercise_add_brickPrasad Desala2018-11-211-3/+3
| | | | | | | Fixed the validation code in test_add_brick_without_volname Change-Id: I5449b6472cc2b6644b833be47233d344a9dd8d1b Signed-off-by: Prasad Desala <tdesala@redhat.com>
* Fix spelling mistake across the codebaseNigel Babu2018-08-072-4/+4
| | | | Change-Id: I46fc2feffe6443af6913785d67bf310838532421
* added an automated dht test case: create directoryKartik_Burmee2018-07-171-0/+294
| | | | | Change-Id: I7534850d317993ee0b4c81ec06c1bdaeaf0d7535 Signed-off-by: Kartik_Burmee <kburmee@redhat.com>
* Shorten all the logs around verify_io_procsYaniv Kaul2018-07-172-6/+4
| | | | | | | | No functional change, just make the tests a bit more readable. It could be moved to a decorator later on, wrapping tests. Change-Id: I484bb8b46907ee8f33dfcf4c960737a21819cd6a Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
* glusto/dht: test case for directory healingSusant Palai2018-07-011-0/+139
| | | | | | | | | | | The test case tests directory healing. If a mkdir happens successfully when a subvol is down, the directory should heal and should have zeroed layout once the subvol is up. Change-Id: Ia2f5747a1008112a5dcebda8a953ee3d2de9f75f Signed-off-by: Susant Palai <spalai@redhat.com>
* TC: Induce holes in layout by removebrick force then lookupPrasad Desala2018-06-301-0/+136
| | | | | | | | | | Objective: When induced holes in the layout by remove brick force, lookup sent on the directory from client should fix the directory layout without any holes or overlaps. Change-Id: If4af10929e8e7d4da93cea80c515e37acf53d34e Signed-off-by: Prasad Desala <tdesala@redhat.com>
* glusto/dht: test lookup of directoriesSusant Palai2018-06-291-0/+280
| | | | | | | | | | | | | | | | | | | | | test: case -1: - bring down a subvol - create a directory so that it does not hash to down subvol - make sure stat is successful on the dir case -2: - create directory - bring down hashed subvol - make sure stat is successful on the dir case -3: - create dir - bringdown unhashed subvol - make sure stat is successful on the dir Change-Id: I9cbd2e7f04c885eaa09414d6b49632cf77dd72ec Signed-off-by: Susant Palai <spalai@redhat.com>
* Adding test case for change owner, group, permission for directoryMohit Agrawal2018-06-292-0/+414
| | | | | | | | | | | | | | | | | 1) Create Dir with some file inside dir 2) Verify dir exists on all bricks as well as mount point 3) Compare dir stat with mount-point and brick location path 4) Change the ownership of directory 5) Compare dir stats with mount-point and brick path 6) Try to change pemission with different user for directory 7) Compare dir stat with mount-point and brick path 8) Try to change permission with different user for directory 9) change permission of directory 10) Compare dir stat with mount-point and brick path 11) Try to change permission with different user for same directory Change-Id: I284842be8c7562d4618d4e69e202c4d80945f1c5 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* TC: Induce holes in layout by remove brick force then fix-layoutPrasad Desala2018-06-291-0/+154
| | | | | | | | | Objective: When induced holes in the layout by remove brick force, fix-layout start should fix the layout without any holes or overlaps. Change-Id: Ie4c47fff11957784044e717c644743263812a0e4 Signed-off-by: Prasad Desala <tdesala@redhat.com>
* glusto/dht: test case to check mkdir hashed to a down subvolumeSusant Palai2018-06-291-0/+155
| | | | | | | | The test case verifies that a mkdir of directory hashed to a down subvolume should fail. Change-Id: I8465f4869c9283d4339c50cdbd56b0256fa11bb9 Signed-off-by: Susant Palai <spalai@redhat.com>
* Adding DHT test case: stop glusterd while rebalance in progressPrasad Desala2018-06-271-0/+218
| | | | | | | Rebalance should proceed even if glusterd is down on a node. Change-Id: I499e8a4e6b42bd7a8153c1d82c8b329a1933e748 Signed-off-by: Prasad Desala <tdesala@redhat.com>
* Adding testcase: Exercise rebalance commandPrasad Desala2018-06-271-0/+376
| | | | | | | | | | | | | This testcase exercises below rebalance commands, 1) Rebalance with fix-layout 2) Rebalance start --> status --> stop 3) Rebalance with force option Changes: - Remove pytest.mark from test cases Change-Id: I467de068dabac90018f6241472b2d91d9d9e85a8 Signed-off-by: Prasad Desala <tdesala@redhat.com>
* Adding Testcase: Rebalance_while_remove_brick_in_progressPrasad Desala2018-06-271-0/+186
| | | | | | | | While remove-brick operation is in-progress on a volume, glusterd should not allow rebalance on the same volume. Change-Id: Ic94754bc12c86a32f2f5fd064129bf6bc038ed6a Signed-off-by: Prasad Desala <tdesala@redhat.com>
* glusto/dht: Verify create file operationSusant Palai2018-06-261-0/+166
| | | | | | | | | | test case: - Verify that the file is created on the hashed subvol alone - Verify that the trusted.glusterfs.pathinfo reflects the file location - Verify that the file creation fails if the hashed subvol is down Change-Id: I951c20f03772a0c5739244ec354f9bbfd6d0ea65 Signed-off-by: Susant Palai <spalai@redhat.com>
* Start rebalance when glusterd is down on one of the nodePrasad Desala2018-06-231-0/+184
| | | | | | | | Rebalance should fail on a pure distribute volume when glusterd is down on one of the nodes. Change-Id: I5a871a7783b434ef61f0f1cf4b262db9f5148af6 Signed-off-by: Prasad Desala <tdesala@redhat.com>
* Adding Testcase: add_brick_while_remove_brick_in_progressPrasad Desala2018-06-211-0/+183
| | | | | | | | While remove-brick operation is in-progress on a volume, glusterd should not allow add-brick operation on the same volume. Change-Id: Iddcbbdb1a5a444ea88995f176c0a18df932dea41 Signed-off-by: Prasad Desala <tdesala@redhat.com>
* Adding Testcase: Remove_brick_while_rebalance_in_progressPrasad Desala2018-06-211-0/+212
| | | | | | | | If a rebalance is in-progress on a volume, glusterd should fail a remove-brick operation on the same volume. Change-Id: I2f15023870f342c98186b1860b960cb3c04c0572 Signed-off-by: Prasad Desala <tdesala@redhat.com>
* Restart glusterd after rebalance is overPrasad Desala2018-06-191-0/+177
| | | | | | | | | Test case objective: Restarting glusterd should not restart a completed rebalance operation. Change-Id: I52b808d91d461048044ac742185ddf4696bf94a3 Signed-off-by: Prasad Desala <tdesala@redhat.com>
generated by cgit (git 2.34.1) at 2024-04-24 17:52:46 +0000