Skip to content

WIP: Obtain Host Panic/Boot Failure Messages#2518

Draft
jamesmunns wants to merge 12 commits into
masterfrom
james/packrattin
Draft

WIP: Obtain Host Panic/Boot Failure Messages#2518
jamesmunns wants to merge 12 commits into
masterfrom
james/packrattin

Conversation

@jamesmunns
Copy link
Copy Markdown
Contributor

Not yet complete.

Closes #2504
Currently based on #2503

Comment thread task/packrat-api/src/lib.rs Outdated
Comment thread task/packrat-api/src/lib.rs Outdated
Comment thread task/packrat-api/src/lib.rs Outdated
Comment thread task/packrat-api/src/lib.rs Outdated
// this would only happen if packrat crashes. We could store some fake info here to
// continue preparing an ereport, but THAT is going to be a problem anyway because
// we send ereports to, you guessed it: packrat, which just crashed.
let response = self
Copy link
Copy Markdown
Contributor Author

@jamesmunns jamesmunns May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's probably something better we can do here as well, the only failure modes for a write_host_bootfail (and host panic) call are:

  1. That's illegal (not supported, OR client dies and revokes the lease)
  2. Packrat died

Neither of these are particulary good things (the former doesn't even matter here), and there might be a better way to express the idolatry IPC API to make this more clear in the generated code.

@jamesmunns
Copy link
Copy Markdown
Contributor Author

MGS message changes are tracked in oxidecomputer/management-gateway-service#495.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

control-plane-agent: Add interface(s) for retrieving Host Panic/Boot Failure messages

2 participants