oxidecomputer / oxidecomputer/omicron

CI: deploy script goes off the rails if external DNS doesn't start

Open
#6,772 6 comments 0 reactions 1 assignee View on GitHub

@iliana is already working on this.

Since Oct 4, 2024.

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

Description

This test failed on a CI run on https://github.com/oxidecomputer/omicron/commit/5198b40290614352be19a4326a482eb1b0213c1e (pre-PR):

https://github.com/oxidecomputer/omicron/runs/31089252234

Log showing the specific test failure:

https://buildomat.eng.oxide.computer/wg/0/details/01J9C20P89V4YQSG2E0ARCWCHT/EYt2W7eh7IIwcossCxtFwwpEOJA28LwZLLIegY835dykgGNr/01J9C216DWS3S4ZRPN1HW8FD0J

Excerpt from the log showing the failure:

1071	2024-10-04T16:21:16.536Z	+ curl -sSf /v1/ping --resolve '' --cacert /opt/oxide/sled-agent/pkg/initial-tls-cert.pem
1072	2024-10-04T16:21:16.559Z	curl: (49) Couldn't parse CURLOPT_RESOLVE entry ''
1073	2024-10-04T16:21:16.559Z	+ [[ 6 -gt 60 ]]

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.