storage-operator: upgrade to v1.42.1 using upgrade-operator-sdk tool #4880
pre-merge.yaml
on: push
changed-files
13s
build-devcontainer
/
build-and-publish-devcontainer
15s
unit_tests_ui
0s
unit_tests_shell_ui
0s
unit_tests_crd_client_generator
0s
build-shell-ui
/
shell-ui
build
/
...
/
build-and-publish-devcontainer
14s
build-docs
/
...
/
build-and-publish-devcontainer
unit_tests_metalk8s_operator
4m 11s
unit_tests_storage_operator
3m 29s
unit_tests_salt
0s
unit_tests_lib_alert_tree
0s
build
/
...
/
build-and-publish-devcontainer
19s
e2e-tests
/
...
/
destroy-multi-node-cluster
7m 16s
e2e-tests
/
...
/
destroy-single-node-cluster
7m 14s
write-final-status
12s
Annotations
12 errors, 12 warnings, and 11 notices
|
unit_tests_storage_operator
Process completed with exit code 2.
|
|
e2e-tests / single-node-e2e / single-node
Canceling since a higher priority waiting request for tests-improvement/bump-operator-sdk-v1.42.1-true exists
|
|
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 / single-node-e2e / single-node
The operation was canceled.
|
|
e2e-tests / multi-node-e2e / multi-node
Canceling since a higher priority waiting request for tests-improvement/bump-operator-sdk-v1.42.1-true exists
|
|
e2e-tests / multi-node-e2e / multi-node
Process completed with exit code 1.
|
|
e2e-tests / multi-node-e2e / multi-node
The operation was canceled.
|
|
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-operator-sdk-v1.42.1-true exists
|
|
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-operator-sdk-v1.42.1-true exists
|
|
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-operator-sdk-v1.42.1-true exists
|
|
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-operator-sdk-v1.42.1-true exists
|
|
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. 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. 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. 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. 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. 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-0d65a14e09.Pre-merge.4880
|
|
build / build-docs / docs
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
build / build
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
build / write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
e2e-tests / single-node-e2e / single-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
e2e-tests / multi-node-e2e / multi-node
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
|
write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-0d65a14e09.Pre-merge.4880
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
scality~metalk8s~KVVTBK.dockerbuild
|
44.5 KB |
sha256:a3ba43527ebd1e469ea89c79eeb2023bb32096cdc557bbcf8190ced9fe3d0aaa
|
|