oxidecomputer / oxidecomputer/omicron
Adding a sled to a rack of theseus fails with CannotSpareAShare
Open
Nobody has claimed this yet.
Add/expunge sled
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
On london, I had expunged and added back sleds 14, 15, and 16.
I then expunged sled 17.
Things went well, and after the expungement of 17, I attempted to add it back.
root@oxz_switch0:~# omdb nexus sleds list-uninitialized
note: Nexus URL not specified. Will pick one from DNS.
note: using DNS server for subnet fd00:1122:3344::/48
note: (if this is not right, use --dns-server to specify an alternate DNS server)
note: using Nexus URL http://[fd00:1122:3344:123::32]:12221
RACK_ID CUBBY SERIAL PART REVISION
255b17ef-3bc7-466c-aef2-c70ba0d9ddaa 17 BRM44220007 913-0000019 6
root@oxz_switch0:~# omdb -w nexus sleds add BRM44220007 913-0000019
note: Nexus URL not specified. Will pick one from DNS.
note: using DNS server for subnet fd00:1122:3344::/48
note: (if this is not right, use --dns-server to specify an alternate DNS server)
note: using Nexus URL http://[fd00:1122:3344:123::32]:12221
Error: adding sled
Caused by:
0: Communication Error: error sending request for url (http://[fd00:1122:3344:123::32]:12221/sleds/add)
1: error sending request for url (http://[fd00:1122:3344:123::32]:12221/sleds/add)
2: operation timed out
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 omdb -w nexus sleds add BRM44220007 913-0000019 and tracing the /sleds/add entry point. Compare the reported CannotSpareAShare behavior with the observed request timeout; done means re-adding the expunged sled completes successfully without either failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100