oxidecomputer / oxidecomputer/omicron
[Neuxs] Report last successful blueprint realized when blueprint realization fails
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
When blueprint realization succeeds, we report the ID of that blueprint: https://github.com/oxidecomputer/omicron/blob/02303a6f03b19b8476fc4bc4a65d6b4e29585c6c/nexus/src/app/background/tasks/blueprint_execution.rs#L112-L115
When blueprint realization fails, we report the ID of the blueprint that failed, too: https://github.com/oxidecomputer/omicron/blob/02303a6f03b19b8476fc4bc4a65d6b4e29585c6c/nexus/src/app/background/tasks/blueprint_execution.rs#L120-L123
But in the failure case, it would be nice to also report the ID of the last blueprint that we succeeded in realizing. (This might be different on different Nexus instances!)
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 in nexus/src/app/background/tasks/blueprint_execution.rs at the success and failure reporting paths linked in the issue. Trace how each Nexus instance tracks blueprint realization results and identify where the last successful blueprint ID is available during failure reporting. Done means failed realization reports both the failed blueprint ID and the last successfully realized blueprint ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100