glusto-tests.git/tests, branch master

[Test] Add TC to test multiple volume shrinks and rebalance

2021-03-09T05:48:28+00:00

Test case:
1. Modify the distribution count of a volume
2. Create a volume, start it and mount it
3. Create some file on mountpoint
4. Collect arequal checksum on mount point pre-rebalance
5. Do the following 3 times:
6. Shrink the volume
7. Collect arequal checksum on mount point post-rebalance
and compare with value from step 4

Change-Id: Ib64575e759617684009c68d8b6bb5f011c553b55
Signed-off-by: Barak Sason Rofman

[Test] Add TC to rebalance highly nested dir structure

2021-03-09T05:44:39+00:00

Test case:
1. Create a volume, start it and mount it
2. On mount point, create a large nested dir structure with files in the
inner-most dir
3. Collect arequal checksum on mount point pre-rebalance
4. Expand the volume
5. Start rebalance and wait for it to finish
6. Collect arequal checksum on mount point post-rebalance and compare
wth value from step 3

Change-Id: I87f0e8df8c4ca850bdf749583635fc8cd2ba1b86
Signed-off-by: Barak Sason Rofman

[Test] Bring down data bricks in cyclic order and trigger heal

2021-03-08T04:28:09+00:00

Change-Id: Ibf0391a2f7709fb08326f57a0c4c899e28faf62f
Signed-off-by: Manisha Saini

[Test]Verify auth functionality with brick down and heal

2021-03-01T06:07:07+00:00

Change-Id: I050525df6cf00fae331e7ddd84661251926e31ca
Signed-off-by: Manisha Saini

[TestFix] Remove temp code from test case

2021-02-17T09:26:59+00:00

Removing temp steps added to verify BZ#1810901

Change-Id: I7d64ed1c797914b8a5b2f0e45271f01a09d51e98
Signed-off-by: Pranav

[Test] Add test to verify permission changes made on mount dir

2021-02-14T18:40:12+00:00

Adding test to verify whether the permission changes
made on the mount point dir is reflected on the brick
dirs as well, even when the change is made while a
brick was down.

1. create pure dist volume
2. mount on client
3. Checked default permission (should be 755)
4. Change the permission to 444 and verify
5. Kill a brick
6. Change root permission to 755
7. Verify permission changes on all bricks, except down brick
8. Bring back the brick and verify the changes are reflected

Change-Id: I0a24b94fc5b75706c664f9e2d1363d38b77f9e3a
Signed-off-by: Pranav

[Test] Verify metadata and data self heal

2021-02-12T04:04:17+00:00

Test: test_metadata_heal_from_shd
Steps:
1. Create, mount and run IO on volume
2. Set `self-heal-daemon` to `off` and bring files into metadata
   split brain
3. Set `self-heal-daemon` to `on` and wait for heal completion
4. Validate areequal checksum on backend bricks

Test: test_metadata_heal_from_heal_cmd
Steps:
1. Create, mount and run IO on volume
2. Set `self-heal-daemon` to `off` and bring files into metadata
   split brain
3. Set `self-heal-daemon` to `on`, invoke `gluster vol  heal`
4. Validate areequal checksum on backend bricks

Test: test_data_heal_from_shd
Steps:
1. Create, mount and run IO on volume
2. Set `self-heal-daemon` to `off` and bring files into data
   split brain
3. Set `self-heal-daemon` to `on` and wait for heal completion
4. Validate areequal checksum on backend bricks

Change-Id: I24411d964fb6252ae5b621c6569e791b54dcc311
Signed-off-by: Leela Venkaiah G

[Test]Test split-brain with hard link and brick down scenario

2021-02-10T06:38:20+00:00

Change-Id: Ib58a45522fc57b5a55207d03b297060b29ab27cf
Signed-off-by: Manisha Saini

[Test]: Add tc to check increase in glusterd memory consumption

2021-02-10T06:34:33+00:00

Test Steps:
1) Enable brick-multiplex and set max-bricks-per-process to 3 in
   the cluster
2) Get the glusterd memory consumption
3) Perform create,start,stop,delete operation for 100 volumes
4) Check glusterd memory consumption, it should not increase by
   more than 50MB
5) Repeat steps 3-4 for two more time
6) Check glusterd memory consumption it should not increase by
   more than 10MB

Upstream issue link: https://github.com/gluster/glusterfs/issues/2142

Change-Id: I54d5e337513671d569267fa23fe78b6d3410e944
Signed-off-by: nik-redhat

[Testfix] Fix I/O logic and change lookup command

2021-02-02T09:47:23+00:00

Problem:
1. I/O command has %s instead of %d for for int.
2. Lookup logic doesn't tigger client heal.

Fix:
Changing to %d and adding a cmd which automatically
triggers heal.

Change-Id: Ibc8a1817894ef755b13c3fee21218adce3ed9c77
Signed-off-by: kshithijiyer