oxidecomputer / oxidecomputer/omicron
Planner flip-flops on which zone to update
Open
@plotnick is already working on this.
Since Jun 9, 2025.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
In our first test of the blueprint-planner background task of #8287, with blueprint execution disabled, we found on setting the target release that the planner produced two blueprints: the first attempted to expunge an internal-dns zone, and the second to update in-place a crucible zone. But it should instead have waited for the first step to complete (which it wouldn't have without enabling execution).
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.