Skip to content

Deployment Test (Azure) #149

Deployment Test (Azure)

Deployment Test (Azure) #149

Triggered via schedule August 23, 2026 00:23
Status Failure
Total duration 35m 4s
Artifacts 3

deployment-test.yaml

on: schedule
init-only
0s
init-only
auth-check
auth-check
oetf
oetf
notify-slack-on-azure-deployment-test-failure
7s
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=1787446721.825369).

Artifacts

Produced during runtime
Name Size Digest
deploy-osmo-32607731861
3.42 KB
sha256:9f9c4e5625cb9191523eac5d4420462a0db51435ba161eaac037754a3e0501ca
tf-destroy-32607731861
42.9 KB
sha256:b719415375aa33e12255951acc9f52efba75a660cf4fa09f1f1d622e972bec24
tf-state-32607731861 Expired
20.5 KB
sha256:e090e253ba0f4eff4004a3f57f44d64fdea77e0c418df77677e708cada3c6b6a