oxidecomputer / oxidecomputer/omicron

something fishy is happening in the `deploy.sh` job during the switch zone check

Open
#9,768 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

https://buildomat.eng.oxide.computer/wg/0/details/01KG5JNVNBG9BBVWG8S874737E/Ar9EJfdSbD1qqfZ2jmuXxeF7mjn15W2b1GpI5ljIsFKgOJNn/01KG5JPR9Q4AHGSK2A6CYK3FPM#S367

Our check that the switch zone is up was, for whatever reason, hanging for approximately 195 seconds on each iteration. During this time according to the 35 MiB of Dendrite logs, Dendrite was handling requests normally.

#9767 slaps a band-aid over the problem to prevent it from kerploding the CI queue length but doesn't get at the root cause.

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

Start with the linked Buildomat run details and inspect the deploy.sh switch-zone-up check alongside the Dendrite logs described in the issue. Review #9767 to understand the temporary mitigation; done means identifying why each check waits about 195 seconds and addressing the root cause so the deploy job no longer stalls.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.