oxidecomputer / oxidecomputer/crucible
Pantry panic: New client:2 uuid:UUID does not match existing Different-UUID
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
A core file from crucible-pantry was found during a customer upgrade:
The panic message was:
thread 'tokio-runtime-worker' panicked at upstairs/src/client.rs:1582:37:
New client:2 uuid:6666df06-b026-436e-aca1-6b5dde713169 does not match existing 9d1b494a-0625-4f53-94c2-37433e128e18 ds_state:Connecting { state: WaitForRegionInfo, mode: Offline } up_state:Active
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 at upstairs/src/client.rs:1582:37 and inspect the client state around the reported UUID mismatch. Trace how a new client is compared with the existing client and determine the expected behavior for the Connecting and Active states. Done means the cause and intended handling of this panic are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100