drive-by: remove unused annotations from fluent-bit #4898
eg-ayoubpre-merge.yaml
on: push
changed-files
14s
build-devcontainer
/
build-and-publish-devcontainer
23s
unit_tests_ui
unit_tests_shell_ui
unit_tests_crd_client_generator
build-shell-ui
/
shell-ui
build
/
...
/
build-and-publish-devcontainer
19s
build-docs
/
...
/
build-and-publish-devcontainer
unit_tests_metalk8s_operator
unit_tests_storage_operator
unit_tests_salt
1m 57s
unit_tests_lib_alert_tree
build
/
...
/
build-and-publish-devcontainer
15s
e2e-tests
/
...
/
destroy-multi-node-cluster
7m 19s
e2e-tests
/
...
/
destroy-single-node-cluster
7m 20s
write-final-status
9s
Annotations
4 errors, 7 warnings, and 9 notices
|
e2e-tests / single-node-e2e / single-node
Process completed with exit code 1.
|
|
e2e-tests / single-node-e2e / single-node
Process completed with exit code 1.
|
|
e2e-tests / multi-node-e2e / multi-node
Process completed with exit code 1.
|
|
e2e-tests / multi-node-e2e / multi-node
Process completed with exit code 1.
|
|
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/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/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 / 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
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|
|
build / write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|
|
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|
|
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|
|
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|
|
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|
|
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|
|
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|
|
write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-2164dbcabd.Pre-merge.4898
|