glusto-tests.git/tests/functional/glusterd, branch master

[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

[Test] Add test to verify df -h output after replace, expand and shrink ops

2021-01-18T13:50:12+00:00

Test to verify the df -h output when for a given volume, the bricks are
replaces, volume size is shrinked and when the volume size is expanded.
Steps:
- Take the output of df -h.
- Replace any one brick for the volumes.
- Wait till the heal is completed
- Repeat steps 1, 2 and 3 for all bricks for all volumes.
- Check if there are any inconsistencies in the output of df -h
- Remove bricks from volume and check output of df -h
- Add bricks to volume and check output of df -h

The size of mount points should remain unchanged during a replace op,
and the sizes should vary according to shrink or expand op performed
on the volume.

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

[TestFix+Lib] Add steps to validate glusterd logs

2021-01-18T05:08:42+00:00

Adding additional checks to verify the glusterd logs
for `Responded to` and `Received ACC` while performing
a glusterd restart.

Replacing reboot with network interface down to validate
the peer probe scenarios.

Adding lib to bring down network interface.

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

[Test] Rebalance should start successfully if name of volume more than 108 chars

2021-01-08T18:16:17+00:00

1. On Node N1, Add "transport.socket.bind-address N1" in the
/etc/glusterfs/glusterd.vol
2. Create a replicate (1X3) and disperse (4+2) volumes with
name more than 108 chars
3. Mount the both volumes using node 1 where you added the
"transport.socket.bind-address" and start IO(like untar)
4. Perform add-brick on replicate volume 3-bricks
5. Start rebalance on replicated volume
6. Perform add-brick for disperse volume 6 bricks
7. Start rebalance of disperse volume

Change-Id: Ibc57f18b84d21439bbd65a665b31d45b9036ca05
Signed-off-by: “Milind <“mwaykole@redhat.com”>

[Test] Change the reserve limits to lower and higher while rebal in-progress

2020-12-21T06:39:29+00:00

1) Create a distributed-replicated volume and start it.
2) Enable storage.reserve option on the volume using below command,
    gluster volume set storage.reserve 50
3) Mount the volume on a client
4) Add some data on the mount point (should be within reserve limits)
5) Now, add-brick and trigger rebalance.
    While rebalance is in-progress change the reserve limit to a lower
    value say (30)
6. Stop the rebalance
7. Reset the storage reserve value to 50 as in step 2
8. trigger rebalance
9. while rebalance in-progress change the reserve limit to a higher
    value say (70)

Change-Id: I1b2e449f74bb75392a25af7b7088e7ebb95d2860
Signed-off-by: “Milind <“mwaykole@redhat.com”>

[TestFix] Adding cluster options reset in TC

2020-12-17T12:56:28+00:00

The cluster options are reset post the TC run
so that they don't persist through the other
TC runs.

Change-Id: Id55bb64ded09e113cdc0fc512a17857195619e41
Signed-off-by: srijan-sivakumar

[Test]: Add tc to detect drop of outbound traffic as network failure in glusterd

2020-12-17T11:58:05+00:00

Test Steps:
1) Create a volume and start it.
2) Add an iptable rule to drop outbound glusterd traffic
3) Check if the rule is added in iptables list
4) Execute few Gluster CLI commands like volume status, peer status
5) Gluster CLI commands should fail with suitable error message

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

[Test]: Add tc to test reserved port range for gluster

2020-12-17T11:51:46+00:00

Test Steps:
1) Set the max-port option in glusterd.vol file to 49200
2) Restart glusterd on one of the node
3) Create 50 volumes in a loop
4) Try to start the 50 volumes in a loop
5) Confirm that the 50th volume failed to start
6) Confirm the error message, due to which volume failed to start
7) Set the max-port option in glusterd.vol file back to default value
8) Restart glusterd on the same node
9) Starting the 50th volume should succeed now

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

[Test] Memory crash - stop and start gluster processes multiple times

2020-12-09T07:16:20+00:00

Steps-
1. Create a gluster volume.
2. Kill all gluster related processes.
3. Start glusterd service.
4. Verify that all gluster processes are up.
5. Repeat the above steps 5 times.

Change-Id: If01788ae8bcdd75cdb55261715c34edf83e6f018
Signed-off-by: Rinku Kothiya 
Signed-off-by: srijan-sivakumar

[Test Fix]: Assertion of default quorum options

2020-12-04T08:51:04+00:00

Fix:
Improved the check for default quorum options on the volume,
to work with the present as well as older default values
Older default value: 51
Current Default value: 51 (DEFAULT)

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