Skip to content
Deploy Cellenics infrastructure on AWS

Deploy Cellenics infrastructure on AWS #529

Sign in to view logs

Deploy Cellenics infrastructure on AWS

Deploy Cellenics infrastructure on AWS #529

Manually triggered November 20, 2024 23:31
@alexvpickeringalexvpickering
⁠ 4c564fa
imdsv2
Status Failure
Total duration 58m 38s
Artifacts –

deploy-infra.yaml

on: workflow_dispatch
load-config  /  setup
2s
load-config / setup
load-config  /  Generate deployment matrix based on the config files
6s
load-config / Generate deployment matrix based on the config files
Matrix: Check that sufficient secrets are specified for environment name
Matrix: Create EKS cluster
Matrix: Configure Kubernetes resources on the EKS cluster
Matrix: Setup logging and monitoring
Report if workflow failed
0s
Report if workflow failed
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 13 warnings
Create EKS cluster (HMS, staging, alexvpickering, ci-users/testing/ci-user-testing)
Process completed with exit code 1.
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Process completed with exit code 1.
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Process completed with exit code 1.
load-config / setup
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
load-config / Generate deployment matrix based on the config files
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Create EKS cluster (HMS, staging, alexvpickering, ci-users/testing/ci-user-testing)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, nick-invision/retry@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 1 failed. Reason: Child_process exited with error code 1
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 2 failed. Reason: Child_process exited with error code 1
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 3 failed. Reason: Child_process exited with error code 1
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 4 failed. Reason: Child_process exited with error code 1
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 5 failed. Reason: Child_process exited with error code 1
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 6 failed. Reason: Child_process exited with error code 1
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 7 failed. Reason: Child_process exited with error code 1
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 8 failed. Reason: Child_process exited with error code 1
Configure Kubernetes resources on the EKS cluster (HMS, staging, alexvpickering, ci-users/testing...
Attempt 9 failed. Reason: Child_process exited with error code 1