oxidecomputer / oxidecomputer/omicron
Update progress may roll-back from 100% completion after an update is complete
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
A customer successfully completed a self-service update several weeks ago, with the System Update page in the console showing 100% progress.
Roughly a week later, one of their sleds went down and the displayed update progress rolled back to 99%, presumably because that sled could not be reached.
This is a confusing user experience as it suggests that there is a potential issue with their fully-completed update.
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 tracing how completed self-service update progress is reported to the System Update page, then examine what happens when a sled becomes unreachable after completion. Reproduce the transition from 100% to 99% if possible; done means a completed update continues to display 100% despite later sled unavailability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100