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

[Test] Add tc to check max-bricks-per-process

2020-06-10T08:51:04+00:00

Test Case:
- Create a gluster cluster
- With brick mux set to disable:
  1.Set cluster.max-bricks-per-process to int and check
    error message(Must fail)
  2.Set cluster.max-bricks-per-process to string(Must fail)
- With brick mux set to enable:
  1.Set cluster.max-bricks-per-process to string(Must fail)
  2.Set cluster.max-bricks-per-process to 0
  3.Set cluster.max-bricks-per-process to 1 and check
    error message.(Must fail)
  4.Set cluster.max-bricks-per-process to int value > 1.

Also fixing small issues observed when running all the tests
in the file.

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

[Test] Add tc to check brickmux with wrong values

2020-06-05T10:01:33+00:00

Test Case:
- Create a gluster cluster
- Set cluster.brick-multiplex value to random string(Must fail)
- Set cluster.brick-multiplex value to random int(Must fail)
- Set cluster.brick-multiplex value to random
  special characters(Must fail)

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

[Testfix] Fix assertIn in test_enabling_brick_mux

2020-05-20T09:23:39+00:00

assertIn statement looks for out in warning_message
which fails every time as it should ideally
look for warning_message in out.

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

[py2to3] Fix bunch of py3 incompatibilities

2020-01-02T07:19:55+00:00

Change-Id: I2e85670e50e3dab8727295c34aa6ec4f1326c19d
Signed-off-by: Valerii Ponomarov

[TC] Gluster cli reset commands behaviour with brick mux

2019-12-23T12:36:20+00:00

Test case steps:
1. Set cluster.brick-multiplex to enabled.
2. Create and start 2 volumes of type 1x3 and 2x3.
3. Check if cluster.brick-multiplex is enabled.
4. Reset the cluster using "gluster v reset all".
5. Check if cluster.brick-multiplex is disabled.
6. Create a new volume of type 2x3.
7. Set cluster.brick-multiplex to enabled.
8. Stop and start all three volumes.
9. Check the if pids match and check if more
   than one pids of glusterfsd is present.

Additional library fix:
Changing the command in check_brick_pid_matches_glusterfsd_pid()
as it won't work when brick-mux is enabled.

From:
cmd = ("ps -eaf | grep glusterfsd |
       " "grep %s.%s | grep -v 'grep %s.%s'"
       % (volname, brick_node, volname, brick_node))

To:
cmd = "pidof glusterfsd"

Change-Id: If7bdde13071732b176a0a2289635319571872e47
Co-authored-by: Vitalii Koriakov 
Signed-off-by: Vitalii Koriakov 
Signed-off-by: kshithijiyer

[Fix] Rename testcase test_enabling_brix_mux.py to test_enabling_brick_mux.py

2019-12-09T14:39:45+00:00

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

[TC] CLI Check for brick multiplexing

2019-12-09T14:30:33+00:00

Test case:
- check if brick multiplex is disable by default
- check for warning message triggering by setting brick-multiplex and
  choosing 'n' in y/n
- check if brick multiplex is disabled after triggering warning message
- check brick multiplex for all possible statuses
  (positive and negative)
- check for brick multiplex status in /var/lib/glusterd/options file

Change-Id: If1f2cba0b932837716f577bd6c4d113659975f91
Co-authored-by: Vitalii Koriakov 
Signed-off-by: Vitalii Koriakov 
Signed-off-by: kshithijiyer