Skip to content
Tests

fix fleet-clusters error missing sub-row element #20188

Sign in to view logs

fix fleet-clusters error missing sub-row element

fix fleet-clusters error missing sub-row element #20188

Re-run triggered April 1, 2026 22:42
@github-actionsgithub-actions[bot]
#17102
a-arias:backport/2.14/2268-fleet-cluster-subwow-pt2
Status Failure
Total duration 31m 29s
Artifacts 38

test.yaml

on: pull_request
e2e-ui-build
2m 15s
e2e-ui-build
unit-test
6m 0s
unit-test
i18n
43s
i18n
lint
1m 43s
lint
check-i18n
1m 10s
check-i18n
check-i18n-links
1m 22s
check-i18n-links
check-e2e-tags
7s
check-e2e-tags
check-cypress-build
43s
check-cypress-build
store-origin
5s
store-origin
a11y-test
6m 21s
a11y-test
Matrix: e2e-test
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 12 warnings
check-cypress-build
Process completed with exit code 1.
check-cypress-build
Property 'clusterLabels' does not exist on type 'FleetClusterDetailsPo'. Did you mean 'clusterTabs'?
check-cypress-build
Cannot find module '../../../../support/qase' or its corresponding type declarations.
e2e-test (admin, @adminUser, @virtualizationMgmt, @fleet)
Process completed with exit code 1.
e2e-test (admin, @adminUser, @manager)
Process completed with exit code 1.
e2e-test (admin, @adminUser, @noVai)
Process completed with exit code 1.
e2e-test (standard_user, @standardUser, @navigation, @extensions)
Process completed with exit code 1.
e2e-test (standard_user, @standardUser, @explorer)
Process completed with exit code 1.
e2e-test (standard_user, @standardUser, @manager)
Process completed with exit code 1.
e2e-test (standard_user, @standardUser, @virtualizationMgmt, @fleet)
Process completed with exit code 1.
e2e-test (standard_user, @standardUser, @components)
Process completed with exit code 1.
e2e-test (standard_user, @standardUser, @charts)
Process completed with exit code 1.
e2e-test (standard_user, @standardUser, @noVai)
Process completed with exit code 1.
e2e-test (admin, @adminUser, @components)
Process completed with exit code 1.
e2e-test (admin, @adminUser, @virtualizationMgmt, @fleet)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (admin, @adminUser, @manager)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (admin, @adminUser, @generic, @globalSettings)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (admin, @adminUser, @noVai)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (standard_user, @standardUser, @navigation, @extensions)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (standard_user, @standardUser, @explorer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (standard_user, @standardUser, @manager)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (standard_user, @standardUser, @virtualizationMgmt, @fleet)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (standard_user, @standardUser, @components)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (standard_user, @standardUser, @charts)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (standard_user, @standardUser, @noVai)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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-test (admin, @adminUser, @components)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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/

Artifacts

Produced during runtime
Name Size Digest
20188-2-artifacts-@adminUser@components Expired
26.8 MB
sha256:832d7c350456533b0fa8a4b8af92f6eb155498a3557980edbcca7dcb7395fecd
20188-2-artifacts-@adminUser@generic@globalSettings Expired
60.3 MB
sha256:1cb378514def2ccfebca0eb10435e4fb70207298773288b31d2b2a49a7b67ce7
20188-2-artifacts-@adminUser@manager Expired
45 MB
sha256:91a20f6d20d6a5c1a4d3692a062d546d21ca6a708e239b11f873359b0705ebfb
20188-2-artifacts-@adminUser@noVai Expired
93.3 MB
sha256:8a06acb1175dea9b1b1e226db7f160f2262923327aa78e1f20da6907d88e0289
20188-2-artifacts-@adminUser@virtualizationMgmt@fleet Expired
38.9 MB
sha256:cfb2805e3484025b3b50ab8f00ac162b87f73a412d4f77755b466a86e46d749e
20188-2-artifacts-@standardUser@charts Expired
20.7 MB
sha256:d6da3d6942b7ad1b8d8c35e02b43d26b4b3e4fab065a97396004475b5d737d3a
20188-2-artifacts-@standardUser@components Expired
20.4 MB
sha256:cb42d1cb2be56edbd221ac5301bbb25405859aeee020228d445e3025884f88d1
20188-2-artifacts-@standardUser@explorer Expired
21.1 MB
sha256:f769a57c58767d1fbfb6be4a336061b89f4bf37678b32ed816eea6d8f5735d58
20188-2-artifacts-@standardUser@manager Expired
20.2 MB
sha256:55f9c37fb0a7fded8ba6851243b0aa18521895941874e4e91203218781b0b77f
20188-2-artifacts-@standardUser@navigation@extensions Expired
20.6 MB
sha256:cb4c8acc4c77603ed845fd2f360ce4d0b5fc81fe9eddd33bb92efe122d2768c6
20188-2-artifacts-@standardUser@noVai Expired
20.7 MB
sha256:54bc2713c730c6d2e3da53f62ebf570a6708d21d0a70d0f07b83231a2e176c28
20188-2-artifacts-@standardUser@virtualizationMgmt@fleet Expired
20.4 MB
sha256:80ba0774769a445125a1fc1a8be9958424396e9b683df03e7640f02c7544c1bd