LU-3703 tests: skip getfattr part of sanity test 234

Test fails due to a known bug in the upstream getfattr command in
SLES clients.  Skip the failing part of the test to work around
this problem.

If the upstream fix already present in source and in RHEL releases ever
lands in SLES releases this mod can be removed.

Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: I153713dc0dd43178d16f3c5bdf79c7ce07b6bbef
Reviewed-on: http://review.whamcloud.com/7306
Tested-by: Hudson
Tested-by: Maloo <whamcloud.maloo@gmail.com>
Reviewed-by: Keith Mannthey <keith.mannthey@intel.com>
Reviewed-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>

diff --git a/lustre/tests/sanity.sh b/lustre/tests/sanity.sh
index 75e3bc1..db9807c 100644 (file)
--- a/lustre/tests/sanity.sh
+++ b/lustre/tests/sanity.sh
@@ -11602,9 +11602,12 @@ test_234() {
        $LCTL set_param fail_loc=0x1405
        setfattr -n user.attr -v value $DIR/$tdir/$tfile &&
                error "setfattr should have failed with ENOMEM"
-       # attr pre-2.4.44-7 had a bug with rc
-       getfattr -n user.attr $DIR/$tdir/$tfile &&
-               error "getfattr should have failed with ENOMEM"
+       if [ ! -f /etc/SuSE-release ]; then
+               # attr pre-2.4.44-7 had a bug with rc
+               # LU-3703 - SLES clients have older attr
+               getfattr -n user.attr $DIR/$tdir/$tfile &&
+                       error "getfattr should have failed with ENOMEM"
+       fi
        $LCTL set_param fail_loc=0x0
        rm -rf $DIR/$tdir