Skip to content

fix: namespace GHCR images under scality/zenko/ to avoid permission c… #8828

fix: namespace GHCR images under scality/zenko/ to avoid permission c…

fix: namespace GHCR images under scality/zenko/ to avoid permission c… #8828

Triggered via push March 25, 2026 16:29
Status Cancelled
Total duration 8m 49s
Artifacts

end2end.yaml

on: push
build-kafka
30s
build-kafka
check-dashboard-versions
15s
check-dashboard-versions
build-test-image
15s
build-test-image
lint-and-build-ctst
37s
lint-and-build-ctst
check-alerts  /  run-alert-tests
32s
check-alerts / run-alert-tests
check-workflows
1m 42s
check-workflows
build-doc
2m 42s
build-doc
check-mongo-patches
19s
check-mongo-patches
end2end-2-shards-http
8m 3s
end2end-2-shards-http
end2end-sharded
8m 3s
end2end-sharded
end2end-pra
0s
end2end-pra
ctst-end2end-sharded
0s
ctst-end2end-sharded
write-final-status
0s
write-final-status
Fit to window
Zoom out
Zoom in

Annotations

14 errors, 11 warnings, and 6 notices
lint-and-build-ctst
Process completed with exit code 1.
build-iso
Canceling since a higher priority waiting request for zenko-tests-improvement/ZENKO-5110-build-our-own-bitnami-image exists
build-iso
The operation was canceled.
end2end-sharded
Canceling since a higher priority waiting request for zenko-tests-improvement/ZENKO-5110-build-our-own-bitnami-image exists
end2end-sharded
Process completed with exit code 1.
end2end-sharded
Process completed with exit code 1.
end2end-sharded
Process completed with exit code 1.
end2end-sharded
The operation was canceled.
end2end-2-shards-http
Canceling since a higher priority waiting request for zenko-tests-improvement/ZENKO-5110-build-our-own-bitnami-image exists
end2end-2-shards-http
Process completed with exit code 1.
end2end-2-shards-http
Process completed with exit code 1.
end2end-2-shards-http
Process completed with exit code 1.
end2end-2-shards-http
The operation was canceled.
build-iso-and-end2end-test
Canceling since a higher priority waiting request for zenko-tests-improvement/ZENKO-5110-build-our-own-bitnami-image exists
build-test-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
check-dashboard-versions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
check-mongo-patches
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-kafka
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
check-alerts / run-alert-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/create-github-app-token@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
lint-and-build-ctst
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/create-github-app-token@v1, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
check-workflows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, scality/action-artifacts@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-doc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, scality/action-artifacts@v4. 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/
build-iso
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/create-github-app-token@v1, docker/login-action@v3, scality/action-artifacts@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
end2end-sharded
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/create-github-app-token@v1, Azure/setup-kubectl@v4, docker/login-action@v3, mikepenz/action-junit-report@v4, scality/action-artifacts@v4. 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/
end2end-2-shards-http
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/create-github-app-token@v1, Azure/setup-kubectl@v4, docker/login-action@v3, mikepenz/action-junit-report@v4, scality/action-artifacts@v4. 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/
check-workflows
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-298ad3c92f.build-iso-and-end2end-test.8828
build-doc
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-298ad3c92f.build-iso-and-end2end-test.8828
end2end-sharded
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-298ad3c92f.build-iso-and-end2end-test.8828
Banzaicloud Charts not available: install-kind-dependencies.sh#L51
Failed to add banzaicloud-stable repo, using local checkout
end2end-2-shards-http
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-298ad3c92f.build-iso-and-end2end-test.8828
Banzaicloud Charts not available: install-kind-dependencies.sh#L51
Failed to add banzaicloud-stable repo, using local checkout