Skip to content

MK8S-197 - Add banner in case of failed to retrieve alerts #4904

MK8S-197 - Add banner in case of failed to retrieve alerts

MK8S-197 - Add banner in case of failed to retrieve alerts #4904

Triggered via push March 23, 2026 15:36
Status Cancelled
Total duration 27m 43s
Artifacts 2

pre-merge.yaml

on: push
changed-files
13s
changed-files
build-devcontainer  /  build-and-publish-devcontainer
19s
build-devcontainer / build-and-publish-devcontainer
build_integration_container_nginx
2m 25s
build_integration_container_nginx
unit_tests_ui
1m 36s
unit_tests_ui
unit_tests_shell_ui
43s
unit_tests_shell_ui
unit_tests_crd_client_generator
0s
unit_tests_crd_client_generator
build-shell-ui  /  shell-ui
build-shell-ui / shell-ui
build  /  ...  /  build-and-publish-devcontainer
12s
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 18s
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
0s
unit_tests_salt
unit_tests_lib_alert_tree
0s
unit_tests_lib_alert_tree
integration_tests_ui
6m 36s
integration_tests_ui
build  /  ...  /  build-and-publish-devcontainer
13s
build / build-docs / build-devcontainer / build-and-publish-devcontainer
build-docs  /  docs
build-docs / docs
build  /  ...  /  docs
2m 8s
build / build-docs / docs
build  /  write-final-status
9s
build / write-final-status
e2e-tests  /  ...  /  multi-node
e2e-tests / multi-node-e2e / multi-node
e2e-tests  /  ...  /  single-node
e2e-tests / single-node-e2e / single-node
e2e-tests  /  ...  /  destroy-multi-node-cluster
e2e-tests / multi-node-e2e / destroy-multi-node-cluster
e2e-tests  /  ...  /  destroy-single-node-cluster
e2e-tests / single-node-e2e / destroy-single-node-cluster
write-final-status
9s
write-final-status
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 11 warnings, and 6 notices
build / build
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-true exists
build / build
The operation was canceled.
Pre merge
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-true exists
Pre merge
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-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/
unit_tests_ui
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_integration_container_nginx
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-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/
integration_tests_ui
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. 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 / 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/
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-71e1980b11.Pre-merge.4904
unit_tests_ui
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-71e1980b11.Pre-merge.4904
build / build-docs / docs
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-71e1980b11.Pre-merge.4904
integration_tests_ui
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-71e1980b11.Pre-merge.4904
build / write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-71e1980b11.Pre-merge.4904
write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-71e1980b11.Pre-merge.4904

Artifacts

Produced during runtime
Name Size Digest
scality~metalk8s~1H3G6J.dockerbuild
44.3 KB
sha256:0dba4af98a140d951c074fee2e9d65edb6c4a10cf902065dd9fc288a6b2c0b89
scality~metalk8s~NXV7A9.dockerbuild
37.6 KB
sha256:38b87e5d770cc24601ee17d0f49324ceae109f1b4b9f15cd18fabe719e472453