Otherwise the error handling we are expecting will be masked by the
preceding image locking check, and is going to be indistinguishable
because the error messages are all the same.
Signed-off-by: Fam Zheng <f...@redhat.com>
Reviewed-by: Max Reitz <mre...@redhat.com>
---
tests/qemu-iotests/087 | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/tests/qemu-iotests/087 b/tests/qemu-iotests/087
index e7bca37..b640cf6 100755
--- a/tests/qemu-iotests/087
+++ b/tests/qemu-iotests/087
@@ -85,6 +85,7 @@ run_qemu <<EOF
"driver": "$IMGFMT",
"id": "disk",
"node-name": "test-node",
+ "lock-mode": "off",
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -97,6 +98,7 @@ run_qemu <<EOF
"options": {
"driver": "$IMGFMT",
"id": "disk",
+ "lock-mode": "off",
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -109,6 +111,7 @@ run_qemu <<EOF
"options": {
"driver": "$IMGFMT",
"id": "test-node",
+ "lock-mode": "off",
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -122,6 +125,7 @@ run_qemu <<EOF
"driver": "$IMGFMT",
"id": "disk2",
"node-name": "disk",
+ "lock-mode": "off",
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -135,6 +139,7 @@ run_qemu <<EOF
"driver": "$IMGFMT",
"id": "disk2",
"node-name": "test-node",
+ "lock-mode": "off",
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -148,6 +153,7 @@ run_qemu <<EOF
"driver": "$IMGFMT",
"id": "disk3",
"node-name": "disk3",
+ "lock-mode": "off",
"file": {
"driver": "file",
"filename": "$TEST_IMG"
--
2.7.4
