Skip to content

Deployment Test (Azure) #153

Deployment Test (Azure)

Deployment Test (Azure) #153

Triggered via schedule August 27, 2026 01:55
Status Failure
Total duration 40m 55s
Artifacts 3

deployment-test.yaml

on: schedule
init-only
init-only
auth-check
auth-check
notify-slack-on-azure-deployment-test-failure
6s
notify-slack-on-azure-deployment-test-failure
Fit to window
Zoom out
Zoom in

Annotations

1 error, 5 warnings, and 6 notices
deploy-osmo
Process completed with exit code 2.
build-images
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, bazel-contrib/setup-bazel@4fd964a13a440a8aeb0be47350db2fc640f19ca8, docker/login-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-images
BAZEL_REMOTE_CACHE_URL not set — cold build will be slow (~60 min)
tf-apply
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, azure/login@v2, hashicorp/setup-terraform@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-osmo
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, azure/login@v2, hashicorp/setup-terraform@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
tf-destroy
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, azure/login@v2, hashicorp/setup-terraform@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
tf-apply
terraform apply starting — expected ~10–15 min (AKS dominates)
tf-apply
resource group is clean — nothing to delete
tf-apply
RG osmo-deployment-ci-rg confirmed in westus2
deploy-osmo
deploy stage starting — chart install + verify-hello, expected ~5–15 min
tf-destroy
terraform destroy starting — expected ~10–15 min
notify-slack-on-azure-deployment-test-failure
Slack notification posted to channel C0A8RJ738KZ (ts=1787798180.104259).

Artifacts

Produced during runtime
Name Size Digest
deploy-osmo-33031643714
2.86 KB
sha256:dff19e9b5381950ef21199bb8e81050fb7d0c51dd547cd3a23212fe0c5336fae
tf-destroy-33031643714
36.4 KB
sha256:06b653976e9a99387756093accaee1359f23824854504b9e797217ffbf833305
tf-state-33031643714
20.2 KB
sha256:13a3b2b80c7a6a46ee6bedd1e753aaecbbe23cb61a2d7bc62ad12e8a02b57508