oxidecomputer / oxidecomputer/omicron
test failed in CI: deploy: Failed to reach switch zone after 30 seconds
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
This test failed on a CI run on #6764 (https://github.com/oxidecomputer/omicron/commit/893980e7d198db0e45436d768ef3e9d3f6ec66cc): https://github.com/oxidecomputer/omicron/runs/31106728412
Log showing the specific test failure: https://buildomat.eng.oxide.computer/wg/0/details/01J9CX1DW3PF08TSAP6C5BR05B/Zs83GkZ6JiGbx3t2CTXBHpCoUgzG5CrV4qZnLi8qriO1jf5U/01J9CX240452EBWJPNW49B9RZK#S359
Excerpt from the log showing the failure:
buskin console login: Oct 5 00:12:08 buskin ufs: NOTICE: alloc: /: file system full
[...]
+ retry=31
+ curl --head --silent -o /dev/null 'http://[fd00:1122:3344:101::2]:12224/'
+ [[ 31 -gt 30 ]]
+ echo 'Failed to reach switch zone after 30 seconds'
+ exit 1
Failed to reach switch zone after 30 seconds
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 with CI run #31106728412 and the linked Buildomat log, focusing on the deploy step around the buskin console output. Determine why the root filesystem became full and why the switch-zone curl check failed; done means the CI test completes without this failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100