glusterfs.git/tests, branch v3.4.2qa3

tests: Change 'volume create' to 'volume create force'

2013-11-27T05:39:30+00:00

Using 'force' when creating volumes prevents errors when creating
bricks in the root partition.
This fixes test bug-823081.t for bug-962226

Change-Id: I210ffda6bdc2cced4bd54755a2b44fdfd05b813b
Original-author: John Smith 
BUG: 962226
Signed-off-by: John Smith 
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/6356
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd: changes in 'volume create' behaviour

2013-11-27T05:39:16+00:00

        Backport of http://review.gluster.org/4740

Note: This patch is needed by oVirt's Gluster Integration Project

BUG: 948729
Change-Id: I7a9d7c36b7e15269f95637cd9061abac6f8a97de
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/6355
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Backport of http://review.gluster.org/6262

2013-11-20T06:11:13+00:00

Change-Id: Id93b6755b9a71044a7ed90ac9c779121160a75e0
BUG: 1030208
Signed-off-by: Vijaykumar M 
Reviewed-on: http://review.gluster.org/6271
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/dht: Treat migration failures due to space constraints as skipped

2013-09-20T06:39:40+00:00

Currently rebalance/remove-brick op's display migration failed count even
for files which failed due to space issues (not enough space for file, or
migration leading to cluster imbalance)

These will now be counted as skipped, and rebalance/remove-brick status
will display the additional counter

BUG: 989846
Change-Id: I4efa7ce69dd43680ff47181afed0c561954c5080
Signed-off-by: shishir gowda 
Reviewed-on: http://review.gluster.org/5977
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

cli: Fix 'status all' xml output when volumes are not started

2013-09-19T17:29:42+00:00

 Backport of 7d9bc0d21408c31651a65a6ec0e67c3b8acd0fde from master

CLI now only outputs one XML document for 'status all' only containing
those volumes which are started.

BUG: 1004218
Change-Id: I119ac40282380886b46a09fd9a19d35115fd869d
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5970
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

tests: Remove grep process entries from pidgrep

2013-09-15T23:16:27+00:00

Problem:
We were picking process with lowest pid from ps|grep
result. However, lowest pid need not be oldest process
as recycling of PIDs can take place.

Solution:
Removed grep process entries from ps entries using
grep -v grep.

Change-Id: I2b9687a05a34cf6358f773183770d69a3fb9eb10
BUG: 858488
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/5930
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

mgmt/glusterd: Update sub_count on remove brick

2013-09-13T16:51:03+00:00

Change-Id: I7c17de39da03c6b2764790581e097936da406695
BUG: 1002556
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/5902
Tested-by: Gluster Build System

cluster/dht: assign layout onto missing directories too

2013-09-10T08:14:48+00:00

The current self-healing algorithm is ignoring missing directories
for assigning new layout. When lookup() is racing against mkdir()
or when self-healing a half-done mkdir(), the layout assignment split
must happen based on the final number of directories, and not the
currently existing number of directories (because we finish mkdir()
of missing directories before hash layout assignment).

Without this fix, concurrent mkdir() and lookup() will step on
each others feet, create a messed up layout on disk, and end up
with different in-memory layouts.

Once two clients have different in-memory layouts, creation of
subdirectory will not arbitrate on the same hashed subvolume and will
result in GFID mismatch of the sub-directory.

Change-Id: Ia47acad67c265060405984c822b4d37512b9dbb3
BUG: 907072
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5871
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

tests: call 'cleanup' at the end of each test (backport BZ 983975)

2013-09-10T00:23:40+00:00

Some tests do not cleanup after themselves. That is bad behaviour and
makes it difficult to run single tests and verify the state of the
system afterwards.

Change-Id: I5cf80a4a996c691e6b82fd9ce9c711951dc26138
Signed-off-by: Kaleb S. KEITHLEY 
BUG: 1004756
Reviewed-on: http://review.gluster.org/5821
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

cli: check for null in is_server_debug_xlator()

2013-09-10T00:21:44+00:00

Command: gluster volume set  diagnostics.client-log-level trace
Expected output:
"volume set: failed: option log-level trace: 'trace' is not valid
(possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE,
TRACE.)"
Current output: gluster cli receives a segmentation fault
Fix: check for NULL before calling strstr

Change-Id: If4c7a85a635849a388cf122543e12349c109643c
BUG: 982174
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/5298
Reviewed-by: Kaushal M 
Tested-by: Gluster Build System 
Reviewed-on: http://review.gluster.org/5814
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Anand Avati