Skip to content

ARO HCP Continuous Deployment #9014

ARO HCP Continuous Deployment

ARO HCP Continuous Deployment #9014

Triggered via workflow run March 31, 2026 13:39
Status Failure
Total duration 30m 30s
Artifacts

aro-hcp-cd.yml

on: workflow_run
preflight
4s
preflight
Deploy CS PR infrastructure  /  deploy_region_rg
11m 33s
Deploy CS PR infrastructure / deploy_region_rg
Deploy integrated DEV infrastructure  /  deploy_region_rg
8m 28s
Deploy integrated DEV infrastructure / deploy_region_rg
Deploy CS PR infrastructure  /  deploy_monitoring
4m 55s
Deploy CS PR infrastructure / deploy_monitoring
Deploy CS PR infrastructure  /  deploy_service_cluster_rg
18m 11s
Deploy CS PR infrastructure / deploy_service_cluster_rg
Deploy CS PR infrastructure  /  deploy_management_cluster_rg
7m 31s
Deploy CS PR infrastructure / deploy_management_cluster_rg
Deploy integrated DEV infrastructure  /  deploy_monitoring
4m 53s
Deploy integrated DEV infrastructure / deploy_monitoring
Deploy integrated DEV infrastructure  /  deploy_service_cluster_rg
17m 56s
Deploy integrated DEV infrastructure / deploy_service_cluster_rg
Deploy integrated DEV infrastructure  /  deploy_management_cluster_rg
7m 38s
Deploy integrated DEV infrastructure / deploy_management_cluster_rg
Deploy services to CS PR  /  deploy_to_management_cluster
Deploy services to CS PR / deploy_to_management_cluster
Deploy services to CS PR  /  deploy_to_service_cluster
Deploy services to CS PR / deploy_to_service_cluster
Deploy services to integrated DEV  /  deploy_to_management_cluster
Deploy services to integrated DEV / deploy_to_management_cluster
Deploy services to integrated DEV  /  deploy_to_service_cluster
Deploy services to integrated DEV / deploy_to_service_cluster
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 8 warnings
Deploy integrated DEV infrastructure / deploy_management_cluster_rg
Process completed with exit code 2.
Deploy CS PR infrastructure / deploy_management_cluster_rg
Process completed with exit code 2.
Deploy integrated DEV infrastructure / deploy_service_cluster_rg
Process completed with exit code 2.
Deploy CS PR infrastructure / deploy_service_cluster_rg
Process completed with exit code 2.
Deploy integrated DEV infrastructure / deploy_region_rg
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@a65d910e8af852a8061c627c456678983e180302. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Deploy CS PR infrastructure / deploy_region_rg
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@a65d910e8af852a8061c627c456678983e180302. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Deploy integrated DEV infrastructure / deploy_monitoring
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@a65d910e8af852a8061c627c456678983e180302. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Deploy integrated DEV infrastructure / deploy_management_cluster_rg
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@a65d910e8af852a8061c627c456678983e180302, azure/setup-helm@1a275c3b69536ee54be43f2070a358922e12c8d4, azure/setup-kubectl@776406bce94f63e41d621b960d78ee25c8b76ede, azure/use-kubelogin@76597ae0fcbaace21b05e13a2cbf8daee2c6e820, oras-project/setup-oras@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Deploy CS PR infrastructure / deploy_monitoring
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@a65d910e8af852a8061c627c456678983e180302. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Deploy CS PR infrastructure / deploy_management_cluster_rg
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@a65d910e8af852a8061c627c456678983e180302, azure/setup-helm@1a275c3b69536ee54be43f2070a358922e12c8d4, azure/setup-kubectl@776406bce94f63e41d621b960d78ee25c8b76ede, azure/use-kubelogin@76597ae0fcbaace21b05e13a2cbf8daee2c6e820, oras-project/setup-oras@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Deploy integrated DEV infrastructure / deploy_service_cluster_rg
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@a65d910e8af852a8061c627c456678983e180302, azure/use-kubelogin@76597ae0fcbaace21b05e13a2cbf8daee2c6e820, oras-project/setup-oras@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Deploy CS PR infrastructure / deploy_service_cluster_rg
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@a65d910e8af852a8061c627c456678983e180302, azure/use-kubelogin@76597ae0fcbaace21b05e13a2cbf8daee2c6e820, oras-project/setup-oras@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/