oxidecomputer / oxidecomputer/omicron

Support bundles should include GZ `/var/fm` contents

Open
#9,548 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

fault-management important non-blocker support-bundles
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

Currently support bundles don't include any fault information that a system can generate. This should be included in support bundles for diagnosability and to help us correlate other issues that are going on. Specifically we should probably add /var/fm to the list of GZ-specific things to include. We should also ensure that some of the rotated FM logs are pruned periodically to ensure that we can't run a ramdisk out of space this way. While things are already in the logrotate commands, it wasn't immediately obviously to me that we ever would clean up or archive those files and not potentially fill up the ramdisk.

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.

Research direction

Locate the support-bundle code that selects GZ-specific contents and the logrotate commands covering FM logs. Confirm how /var/fm is gathered and how rotated logs are retained or pruned; done means support bundles include the requested fault information without allowing the ramdisk to fill.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devops, observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.