oxidecomputer / oxidecomputer/omicron
[wicket] Don't fail update if host is already in A2.
Open
Nobody has claimed this yet.
wicket
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Tried to re-run an update on a sled that had failed trying to update at the write host-boot-flash step. A step that happens while it's in A2. Easy enough to workaround by just powering it on but would be nice if wicket didn't fail here.
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 locating wicket’s update handling for the write host-boot-flash step and the sled state transition into A2. Inspect the retry path for a sled already in A2, then verify that re-running the update no longer fails and that the sled reaches the intended update state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100