oxidecomputer / oxidecomputer/dendrite
vlans should be regularly ensured - not just once at startup
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 4
Description
Originally filed as https://github.com/oxidecomputer/dendrite-archived/issues/750
After rebooting the scrimlet attached to the switch recently added to madrid, it came up with only one techport. techport1 was present on the system but techport0 was missing.
Logs were collected along with a gcore of dlmgmtd and a kernel dump. All that is located at /net/catacomb/data/staff/ry/no-techport-0.
The link lights on the missing techport were blinking.
Contributor guide
No contributing guide indexed for this repository
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
No source file, test, or entry point is named. Start by reviewing how VLANs and techports are ensured after startup, then inspect the collected diagnostics at /net/catacomb/data/staff/ry/no-techport-0; done means both techports are restored and remain ensured after a reboot or subsequent loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100