diff options
| author | Eric Blake | 2018-03-12 22:11:56 +0100 |
|---|---|---|
| committer | Eric Blake | 2018-03-13 21:38:55 +0100 |
| commit | 6eba9f01bbfbd92ddd5520be83520df06805dabb (patch) | |
| tree | 3e5d708d75bb4a9fe6f95b4ca88ed5ebb93c18e1 /nbd | |
| parent | Merge remote-tracking branch 'remotes/ehabkost/tags/python-next-pull-request'... (diff) | |
| download | qemu-6eba9f01bbfbd92ddd5520be83520df06805dabb.tar.gz qemu-6eba9f01bbfbd92ddd5520be83520df06805dabb.tar.xz qemu-6eba9f01bbfbd92ddd5520be83520df06805dabb.zip | |
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>
Diffstat (limited to 'nbd')
0 files changed, 0 insertions, 0 deletions