Commit c64c3ae3 authored Aug 15, 2019 by Max Reitz

iotests: Disable 110 for vmdk.twoGbMaxExtentSparse



The error message for the test case where we have a quorum node for
which no directory name can be generated is different: For
twoGbMaxExtentSparse, it complains that it cannot open the extent file.
For other (sub)formats, it just notes that it cannot determine the
backing file path.  Both are fine, but just disable twoGbMaxExtentSparse
for simplicity's sake.

Signed-off-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Message-id: 20190815153638.4600-7-mreitz@redhat.com
Reviewed-by: John Snow <jsnow@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>

parent 325dd915

tests/qemu-iotests/110

+2 −1

Original line number	Diff line number	Diff line
		@@ -40,7 +40,8 @@ trap "_cleanup; exit \$status" 0 1 2 3 15
		# Any format supporting backing files
		_supported_fmt qed qcow qcow2 vmdk
		_supported_proto file
		_unsupported_imgopts "subformat=monolithicFlat" "subformat=twoGbMaxExtentFlat"
		_unsupported_imgopts "subformat=monolithicFlat" "subformat=twoGbMaxExtentFlat" \
		"subformat=twoGbMaxExtentSparse"

		TEST_IMG_REL=$(basename "$TEST_IMG")