The problem that the 2.9 disk images upgraded to 2.10 caused
is fixed. We can now add back the use of the 2.9 disk image
into the t32_check routine used by conf-sanity test 32*.
Signed-off-by: James Nunez <james.a.nunez@intel.com>
Change-Id: I5c32c05ba31c525d6ff46fbd6ba5edab7368a86b
Reviewed-on: https://review.whamcloud.com/27295
Tested-by: Jenkins
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Wei Liu <wei3.liu@intel.com>
Reviewed-by: Saurabh Tandan <saurabh.tandan@intel.com>
local IMGTYPE=$(facet_fstype $SINGLEMDS)
local IMGTYPE=$(facet_fstype $SINGLEMDS)
- tarballs=$($r find $RLUSTRE/tests -maxdepth 1 -name \'disk*-$IMGTYPE.tar.bz2\' | grep -v "2_9")
+ tarballs=$($r find $RLUSTRE/tests -maxdepth 1 \
+ -name \'disk*-$IMGTYPE.tar.bz2\')
if [ -z "$tarballs" ]; then
skip "No applicable tarballs found"
if [ -z "$tarballs" ]; then
skip "No applicable tarballs found"