iotests: Fix stuck NBD process on 33
Commit afe35cde6 added additional actions to test 33, but forgot to reset the image between tests. As a result, './check -nbd 33' fails because the qemu-nbd process from the first half is still occupying the port, preventing the second half from starting a new qemu-nbd process. Worse, the failure leaves a rogue qemu-nbd process behind even after the test fails, which causes knock-on failures to later tests that also want to start qemu-nbd. Reported-by: Max Reitz <mreitz@redhat.com> Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <20180312211156.452139-1-eblake@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com>
This commit is contained in:
parent
026aaf47c0
commit
6eba9f01bb
@ -105,6 +105,7 @@ for align in 512 4k; do
|
||||
done
|
||||
done
|
||||
|
||||
_cleanup_test_img
|
||||
|
||||
# Trigger truncate that would shrink qcow2 L1 table, which is done by
|
||||
# clearing one entry (8 bytes) with bdrv_co_pwrite_zeroes()
|
||||
|
Loading…
x
Reference in New Issue
Block a user