iotests/283: Use consistent size for source and target

The test case forgot to specify the null-co size for the target node.
When adding a check to backup that both sizes match, this would fail
because of the size mismatch and not the behaviour that the test really
wanted to test.

Fixes: a541fcc27c
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20200430142755.315494-2-kwolf@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
(cherry picked from commit 813cc2545b)
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
stable-4.2
Kevin Wolf 2020-04-30 16:27:52 +02:00 committed by Michael Roth
parent 0664ffac4b
commit 4a0db6ba7d
2 changed files with 6 additions and 2 deletions

View File

@ -72,7 +72,11 @@ to check that crash is fixed :)
vm = iotests.VM()
vm.launch()
vm.qmp_log('blockdev-add', **{'node-name': 'target', 'driver': 'null-co'})
vm.qmp_log('blockdev-add', **{
'node-name': 'target',
'driver': 'null-co',
'size': size,
})
vm.qmp_log('blockdev-add', **{
'node-name': 'source',

View File

@ -1,4 +1,4 @@
{"execute": "blockdev-add", "arguments": {"driver": "null-co", "node-name": "target"}}
{"execute": "blockdev-add", "arguments": {"driver": "null-co", "node-name": "target", "size": 1048576}}
{"return": {}}
{"execute": "blockdev-add", "arguments": {"driver": "blkdebug", "image": {"driver": "null-co", "node-name": "base", "size": 1048576}, "node-name": "source"}}
{"return": {}}