oxidecomputer / oxidecomputer/omicron
Distributed disks ended showing up as 'FAULTED' after running terraform script
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
The following distributed disks show up 'FAULTED' after a stress test ran using terraform.
Earlier, I was able to delete one (not present in the list), so it's not super bad, but still. No zones attached to these show up.
This happened with the previous build in Dogfood (20.0.0-0.ci+git13937a135d7).
Dogfood has been updated to a more recent one since then (20.0.0-0.ci+gita3fee0ec59c).
In Console: https://oxide.sys.rack2.eng.oxide.computer/projects/verdant-df/disks
03c2a9f0-240e-4271-9eef-1f2c82aee7fa 4 GiB crucible faulted deleted-03c2a9f0-240e-4271-9eef-1f2c82aee7fa -
36d43a03-2424-4480-8587-fd38dae97ea4 4 GiB crucible faulted deleted-36d43a03-2424-4480-8587-fd38dae97ea4 -
42a76b78-900f-4440-8f2d-f37bb1efd680 4 GiB crucible faulted deleted-42a76b78-900f-4440-8f2d-f37bb1efd680 -
474b0300-c3d6-432d-8830-93c1743f30e4 4 GiB crucible faulted deleted-474b0300-c3d6-432d-8830-93c1743f30e4 -
cc0c2db7-980a-4b9e-89eb-5417d2579840 5 GiB local faulted deleted-cc0c2db7-980a-4b9e-89eb-5417d2579840 -
d40e1e6d-563d-4884-bfb2-e33dd38803c0 4 GiB crucible faulted deleted-d40e1e6d-563d-4884-bfb2-e33dd38803c0 -
e02cb40c-45e8-4f95-9f4c-b83d10b97a44 5 GiB local faulted deleted-e02cb40c-45e8-4f95-9f4c-b83d10b97a44 -
e5f18761-308d-445d-a34b-2ad73819bc7b 4 GiB crucible faulted deleted-e5f18761-308d-445d-a34b-2ad73819bc7b -
eaff172b-67d9-411f-ad78-fe70c048c33a 5 GiB local faulted deleted-eaff172b-67d9-411f-ad78-fe70c048c33a -
f4a69ecb-b424-4c53-a82b-c200abd28076 4 GiB crucible faulted deleted-f4a69ecb-b424-4c53-a82b-c200abd28076 -
f6183b4b-9bb3-4db3-beca-1638f1db99e1 5 GiB local faulted deleted-f6183b4b-9bb3-4db3-beca-1638f1db99e1 -
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.
Research direction
Start by reproducing the Terraform stress test against the Dogfood disk list in Console, comparing the reported build with the newer build. Done means determining why distributed disks remain FAULTED with deleted names and no zones, then verifying that the behavior no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, terraform
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100