oxidecomputer / oxidecomputer/hubris
perhaps `mgs_sidecar` should report an ereport when it can't read the RoT lifecycle state
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
As @jamesmunns noted in #2694, we may want to say something when we attempt to unlock the techport but can't talk to the RoT:
Do we want to add an ereport for this now (probably once per boot-cycle, or at least edge-triggered)? It might be good to surface this upstack for future alerting.
Originally posted by @jamesmunns in https://github.com/oxidecomputer/hubris/pull/2694#discussion_r4035915118
I'm not sure if this is actually worth an ereport or not, since the only time we've seen this happen is transiently while the RoT is in reset. Maybe what we should really do is like, produce an ereport if we see this persistently for a long time period or something?
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 reading the discussion in #2694 and the mgs_sidecar path that reads the RoT lifecycle state. Clarify whether transient failures during RoT reset should be reported and what persistent or edge-triggered behavior means; done requires an agreed ereport policy and corresponding implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100