oxidecomputer / oxidecomputer/omicron

Re-enable stuck saga health check for update status

Open
#10,538 8 comments 0 reactions 1 assignee View on GitHub

@karencfv is already working on this.

Since Jun 3, 2026.

Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

As a follow up to https://github.com/oxidecomputer/omicron/issues/10531, and to make sure we only retrieve sagas that are relevant to the update process, we should retrieve sagas from the Nexus nodes, not the DB.

This should make the contact_support boolean in the update status API more reliable.

This approach has been abandoned, now we will explicitly abandon sagas that fail to recover due to non-transient reasons https://github.com/oxidecomputer/omicron/issues/10581, and re-enable the stuck sagas check exactly as it was before.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.