Skip to content
PR Deploy and Test

VED-318: Multiple entries of System - http://snomed.info/sct is not allowing for SITE & ROUTE but allowing for VACCINECODE and EXTENSION #2328

Sign in to view logs

VED-318: Multiple entries of System - http://snomed.info/sct is not allowing for SITE & ROUTE but allowing for VACCINECODE and EXTENSION

VED-318: Multiple entries of System - http://snomed.info/sct is not allowing for SITE & ROUTE but allowing for VACCINECODE and EXTENSION #2328

Triggered via pull request April 21, 2026 13:24
@Thomas-BoyleThomas-Boyle
synchronize #1405
ved-318-multiple-entries-system-site-route
Status Failure
Total duration 5m 58s
Artifacts 20

pr-deploy-and-test.yml

on: pull_request
run-quality-checks  /  Lint specification
18s
run-quality-checks / Lint specification
run-quality-checks  /  Lint Python projects
32s
run-quality-checks / Lint Python projects
run-quality-checks  /  Lint Terraform projects
8s
run-quality-checks / Lint Terraform projects
run-quality-checks  /  Test Coverage and SonarCloud
4m 21s
run-quality-checks / Test Coverage and SonarCloud
Matrix: deploy-pr-backend / deploy-lambda-images
deploy-pr-backend  /  terraform-plan
45s
deploy-pr-backend / terraform-plan
deploy-pr-backend  /  terraform-apply
deploy-pr-backend / terraform-apply
Matrix: run-e2e-automation-tests
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 9 warnings
deploy-pr-backend / terraform-plan
Process completed with exit code 2.
deploy-pr-backend / terraform-plan
Terraform exited with code 1.
deploy-pr-backend / Deploy recordforwarder image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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-pr-backend / Deploy filenameprocessor image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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-pr-backend / Deploy delta_backend image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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-pr-backend / Deploy mesh_processor image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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-pr-backend / Deploy batch_processor_filter image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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-pr-backend / Deploy mns_publisher image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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-pr-backend / Deploy redis_sync image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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-pr-backend / Deploy id_sync image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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-pr-backend / Deploy backend image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/

Artifacts

Produced during runtime
Name Size Digest
NHSDigital~immunisation-fhir-api~4PLZXP.dockerbuild
44.9 KB
sha256:c5b2307338f096d2775bf6703a16c7ed0a5f9194e56d0c91b2d890a93a6cbd61
NHSDigital~immunisation-fhir-api~8G8P3J.dockerbuild
38.8 KB
sha256:0c78473e650a3a1306bfad0f95af9b5b04cff9f46b29f0c2f723268bc580c589
NHSDigital~immunisation-fhir-api~A69DT5.dockerbuild
38.8 KB
sha256:3bf2d133e7e6ccc0d649db2eda0f4577231ff3e6886e0a02593989fe9694b0fc
NHSDigital~immunisation-fhir-api~CH9JQP.dockerbuild
39.1 KB
sha256:d9918af59e04223b57f80e61ea6834186ebd3fe984db053e43517988fc72d0b1
NHSDigital~immunisation-fhir-api~JZHB0G.dockerbuild
38.8 KB
sha256:e401cb2bb72a4110ba78c207f367d70473b8b3d866ae5fad3251d002a8a9ac4b
NHSDigital~immunisation-fhir-api~QMPAJA.dockerbuild
39.3 KB
sha256:56bec512508ca42692e4d74c802a130b1c95662bec8c9d30f82c6549c3ec4b77
NHSDigital~immunisation-fhir-api~WJF40O.dockerbuild
39 KB
sha256:898241d4beaa132a821f1a21260661418ecccdf9b375b81677ef46c18a7778d6
NHSDigital~immunisation-fhir-api~X39BYN.dockerbuild
39 KB
sha256:c086e3a49f6c1b54b544f1290649f7c52ea5d4c5ba7130ed421b5f417d8dc364
NHSDigital~immunisation-fhir-api~YDE5Z5.dockerbuild
39.2 KB
sha256:450bdbd2484f67ea9a2a49ee0bc3a61f67d60cf2db2996b5dcf9b5654f94d048
deploy-manifest-ack-backend-dev-pr-1405-1
616 Bytes
sha256:f8447e204a099861e6d957c694df0306477871ce91a8699226e83d38731baac4
deploy-manifest-backend-dev-pr-1405-1
607 Bytes
sha256:320e684a4c4ffcec725c9252e7c5c130f7146c1bc2309b136ccb19f788bbd606
deploy-manifest-batch_processor_filter-dev-pr-1405-1
656 Bytes
sha256:86a9bbcd17a466c61f9373dbe81ae95fbf1e4cdc7a4d9e34f67141973b6485ea
deploy-manifest-delta_backend-dev-pr-1405-1
629 Bytes
sha256:90050b9057d2654b2e2af4c1352625939044f68c6120162bbce6ea229f034528
deploy-manifest-filenameprocessor-dev-pr-1405-1
636 Bytes
sha256:47f857b10474cfdb5786b2612092c580eebe20cd46c3cccb302f5b64ec3803e7
deploy-manifest-id_sync-dev-pr-1405-1
612 Bytes
sha256:0a70ccf330dedb50af985bd1d3c10e7493fd2cae66e1096fc73d153becc743c8
deploy-manifest-mesh_processor-dev-pr-1405-1
633 Bytes
sha256:fde8e8c26d64043221c16452ce60cf77c2406affb489421749816be161dc82bc
deploy-manifest-mns_publisher-dev-pr-1405-1
629 Bytes
sha256:795c7a55bbf6c18a268eaae6a22dda23eefb8509917409951376949a0dd82b85
deploy-manifest-recordforwarder-dev-pr-1405-1
632 Bytes
sha256:8cced9364ea2d01186778530e834fa98ea7b1fc65556ea1a7ab6f05d5fdb65db
deploy-manifest-recordprocessor-dev-pr-1405-1
623 Bytes
sha256:0fc43f67bc8d56736a747d85f1274243e38d18899a735e531cae856bbf02c205
deploy-manifest-redis_sync-dev-pr-1405-1
620 Bytes
sha256:21db5d1b6548beb025b9105c59108baaa6460f09754630f41235205e0f34f310