Since about Feb 25 the on_push_main workflow Deploy Dev step seems to be reporting that if failed when we merge and it deploys to dev.
See example: https://github.com/bcgov/traction/actions/runs/22679280907/job/65745215242
Run cp trust-over-ip-configurations/services/traction/charts/dev/values.yaml ./dev-values.yaml
cp trust-over-ip-configurations/services/traction/charts/dev/values.yaml ./dev-values.yaml
yq e -i 'del(.traction) | . *= load("trust-over-ip-configurations/services/traction/charts/dev/values.yaml").traction' ./dev-values.yaml
helm upgrade --install traction -f ./dev-values.yaml --set acapy.image.tag=sha-1e0e88d --set tenant_proxy.image.tag=sha-1e0e88d --set ui.image.tag=sha-1e0e88d ./charts/traction --wait
shell: /usr/bin/bash -e {0}
env:
KUBECONFIG: /home/runner/work/traction/traction/kubeconfig.yaml
Error: UPGRADE FAILED: context deadline exceeded
Error: Process completed with exit code 1.
But the deployment in OCP appears to have succeeded (?), the pod is deployed and the hash for the build image matches the GH commit last merged:
(same for Tenant UI and Proxy)
Since about Feb 25 the
on_push_mainworkflow Deploy Dev step seems to be reporting that if failed when we merge and it deploys to dev.See example: https://github.com/bcgov/traction/actions/runs/22679280907/job/65745215242
But the deployment in OCP appears to have succeeded (?), the pod is deployed and the hash for the build image matches the GH commit last merged:
(same for Tenant UI and Proxy)