We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is reproducible for me right now:
$ oxide --debug disk import --path debian-11-genericcloud-amd64.raw --disk debian-boo --project test-project --description debian --snapshot debian-import --image debian --image-description debian --image-os debian --image-version 11 [00:00:00] [█░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 119.00 MiB/2.00 GiB (833.21 MiB/s, 2s)sending chunk to thread failed with SendError { .. } channel closed
I have not yet determined what the underlying cause is. It'd be helpful if the CLI gave more context about what happened here.
The text was updated successfully, but these errors were encountered:
On the server side I think one of the requests failed with a 500:
16:33:50.143Z INFO f45dcde1-e10d-440b-ade6-a9ab6f283652 (dropshot_external): request completed error_message_external = Internal Server Error error_message_internal = error sending bulk write to pantry: Communication Error: error sending request for url (http://[fd00:1122:3344:102::5]:17000/crucible/pantry/0/volume/b6db3011-b1cd-43f5-a1e6-611248d65a00/bulk_write): error writing a body to connection: Broken pipe (os error 32) file = /home/build/.cargo/git/checkouts/dropshot-a4a923d29dccc492/ff87a01/dropshot/src/server.rs:841 latency_us = 371589 local_addr = 172.30.2.6:443 method = POST remote_addr = 172.20.2.70:46781 req_id = 852eddaa-2464-4844-8211-6628a664495c response_code = 500 uri = //v1/disks/debian-boo/bulk-write?project=test-project
Sorry, something went wrong.
No branches or pull requests
This is reproducible for me right now:
I have not yet determined what the underlying cause is. It'd be helpful if the CLI gave more context about what happened here.
The text was updated successfully, but these errors were encountered: