oxidecomputer / oxidecomputer/omicron
Verify all zones are running as part of CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
With the recent changes to zones to be self assembled, the tests might see the zone "booting" successfully, but the services could be failing to start correctly.
Unless the end to end tests call an API that interacts with that service, a failure could go completely unnoticed. An example can be seen with this comment thread in GitHub https://github.com/oxidecomputer/omicron/pull/4534#discussion_r1456613582
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 CI and end-to-end test setup for zones, then review the linked discussion in PR #4534. Determine where tests currently observe a zone becoming booting and define completion as CI detecting services that fail to start even when no API call exercises them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, distributed-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100