
If the mirror attempt failed and we were able to report an error to the user, it makes no sense to attempt a retry. We don't have a way to abort a mirror attempt yet, so if the user got a setting wrong and it's failing for that reason, the only recourse they'd have would be to restart the server.
39 lines
1017 B
Ruby
Executable File
39 lines
1017 B
Ruby
Executable File
#!/usr/bin/env ruby
|
|
|
|
# Simulate a server which has a disc of the wrong size attached: send
|
|
# a valid NBD hello with a random size, then check that we have see an
|
|
# EOF on read.
|
|
|
|
require 'flexnbd/fake_dest'
|
|
include FlexNBD
|
|
Thread.abort_on_exception = true
|
|
|
|
addr, port = *ARGV
|
|
server = FakeDest.new( addr, port )
|
|
client = server.accept
|
|
|
|
t = Thread.new do
|
|
# The sender *should not reconnect.* Since this is a first-pass
|
|
# mirror attempt, the user will have been told that the mirror failed,
|
|
# so it makes no sense to continue. This means we have to invert the
|
|
# sense of the exception.
|
|
begin
|
|
client2 = server.accept( "Timed out waiting for a reconnection",
|
|
FlexNBD::MS_RETRY_DELAY_SECS + 1 )
|
|
client2.close
|
|
fail "Unexpected reconnection."
|
|
rescue Timeout::Error
|
|
end
|
|
end
|
|
|
|
client.write_hello( :size => :wrong )
|
|
|
|
t.join
|
|
|
|
# Now check that the source closed the first socket (yes, this was an
|
|
# actual bug)
|
|
|
|
fail "Didn't close socket" unless client.disconnected?
|
|
|
|
exit 0
|
|
|