Skip to content

MK8S-184 - Add __init__ in the unit/script folder #4918

MK8S-184 - Add __init__ in the unit/script folder

MK8S-184 - Add __init__ in the unit/script folder #4918

Triggered via push March 24, 2026 15:20
Status Success
Total duration 2h 22m 18s
Artifacts 1

pre-merge.yaml

on: push
changed-files
12s
changed-files
build-devcontainer  /  build-and-publish-devcontainer
26s
build-devcontainer / build-and-publish-devcontainer
build_integration_container_nginx
build_integration_container_nginx
unit_tests_ui
unit_tests_ui
unit_tests_shell_ui
unit_tests_shell_ui
unit_tests_crd_client_generator
unit_tests_crd_client_generator
build-shell-ui  /  shell-ui
build-shell-ui / shell-ui
build  /  ...  /  build-and-publish-devcontainer
14s
build / build-devcontainer / build-and-publish-devcontainer
build-docs  /  ...  /  build-and-publish-devcontainer
build-docs / build-devcontainer / build-and-publish-devcontainer
build  /  ...  /  shell-ui
1m 10s
build / build-shell-ui / shell-ui
unit_tests_metalk8s_operator
0s
unit_tests_metalk8s_operator
unit_tests_storage_operator
0s
unit_tests_storage_operator
unit_tests_salt
1m 57s
unit_tests_salt
unit_tests_lib_alert_tree
unit_tests_lib_alert_tree
integration_tests_ui
integration_tests_ui
build  /  ...  /  build-and-publish-devcontainer
15s
build / build-docs / build-devcontainer / build-and-publish-devcontainer
build-docs  /  docs
build-docs / docs
build  /  ...  /  docs
2m 7s
build / build-docs / docs
build  /  write-final-status
9s
build / write-final-status
e2e-tests  /  ...  /  multi-node
1h 50m
e2e-tests / multi-node-e2e / multi-node
e2e-tests  /  ...  /  single-node
1h 11m
e2e-tests / single-node-e2e / single-node
e2e-tests  /  ...  /  destroy-multi-node-cluster
7m 19s
e2e-tests / multi-node-e2e / destroy-multi-node-cluster
e2e-tests  /  ...  /  destroy-single-node-cluster
7m 18s
e2e-tests / single-node-e2e / destroy-single-node-cluster
write-final-status
9s
write-final-status
Fit to window
Zoom out
Zoom in

Annotations

1 error, 12 warnings, and 11 notices
e2e-tests / single-node-e2e / single-node
Process completed with exit code 1.
build-devcontainer / build-and-publish-devcontainer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, 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/
build / build-devcontainer / build-and-publish-devcontainer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
build / build-docs / build-devcontainer / build-and-publish-devcontainer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
build / build-shell-ui / shell-ui
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@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/
build / build-docs / docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v2, 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 / write-final-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
e2e-tests / single-node-e2e / single-node
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, actions/setup-node@v3, hashicorp/setup-terraform@v2, 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/
e2e-tests / single-node-e2e / destroy-single-node-cluster
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3, hashicorp/setup-terraform@v2, 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/
e2e-tests / multi-node-e2e / multi-node
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, actions/setup-node@v3, hashicorp/setup-terraform@v2, 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/
e2e-tests / multi-node-e2e / destroy-multi-node-cluster
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3, hashicorp/setup-terraform@v2, 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/
write-final-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 / build-shell-ui / shell-ui
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
build / build-docs / docs
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
build / build
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
build / write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918
write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-377a07a9ab.Pre-merge.4918

Artifacts

Produced during runtime
Name Size Digest
scality~metalk8s~4P8B0P.dockerbuild
47.1 KB
sha256:54fe0f5c592b6f41f6aa3b3677152e864ecda3c39fd43bcbc160fc4d36615e16