oxidecomputer / oxidecomputer/omicron
Image stuck in "importing from bulk writes" state.
Open
@jmpesp is already working on this.
Since May 2, 2023.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I was running the following script to test external networking.
#!/bin/bash
for i in `seq 0 500`; do
banner "lap $i"
oxide snapshot delete --project myproj --snapshot loop-snapshot
oxide disk delete --project myproj --disk loop
oxide-import disk import \
--path ~/focal-server-cloudimg-amd64.raw \
--disk-name loop \
--project myproj \
--description "I hate descriptions this one too" \
--snapshot-name loop-snapshot \
--image-description "loop" \
--image-os focal \
--image-version 3 --threads 8
done
When I hit this.
trying to unwind, stopping the bulk write process for Name("loop") failed with Error Response: status: 500 Internal Server Error
This got the image suck in an importing from bulk writes state. Subsequent attempts to delete the image/disk failed.
ry@atrium ~ $ oxide snapshot delete --project myproj --snapshot loop-snapshot
error
Error Response: status: 404 Not Found; headers: {"content-type": "application/json", "x-request-id": "1d5010ac-4e45-4351-b0fb-24549768bb1d", "content-length": "156", "date": "Tue, 02 May 2023 09:15:11 GMT"}; value: Error { error_code: Some("ObjectNotFound"), message: "not found: snapshot with name \"loop-snapshot\"", request_id: "1d5010ac-4e45-4351-b0fb-24549768bb1d" }
ry@atrium ~ $ oxide disk delete --project myproj --disk loop
error
Error Response: status: 400 Bad Request; headers: {"content-type": "application/json", "x-request-id": "f537857a-ce4c-4602-8b08-c5f356043ebb", "content-length": "171", "date": "Tue, 02 May 2023 09:15:14 GMT"}; value: Error { error_code: Some("InvalidRequest"), message: "disk cannot be deleted in state \"importing_from_bulk_writes\"", request_id: "f537857a-ce4c-4602-8b08-c5f356043ebb" }
I stashed the nexus log at /net/catacomb/data/staff/ry/omicron/may-2-import-issue-nexus-log.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.