Skip to content

integration-tests #5569

integration-tests

integration-tests #5569

Triggered via schedule April 3, 2026 06:28
Status Failure
Total duration 49m 4s
Artifacts 22

integration_test.yaml

on: schedule
Cross controller integration test using private-endpoint  /  Plan
12s
Cross controller integration test using private-endpoint / Plan
Integration test using private-endpoint  /  Plan
12s
Integration test using private-endpoint / Plan
Matrix: Runner tests across bases
Matrix: Cross controller integration test using private-endpoint / build
Matrix: Cross controller integration test using private-endpoint / Integration tests / Integration tests
Matrix: Integration test using private-endpoint / build
Matrix: Integration test using private-endpoint / Integration tests / Integration tests
Cross controller integration test using private-endpoint  /  Plan Image Scanning
6s
Cross controller integration test using private-endpoint / Plan Image Scanning
Integration test using private-endpoint  /  Plan Image Scanning
5s
Integration test using private-endpoint / Plan Image Scanning
Matrix: Cross controller integration test using private-endpoint / scan
Matrix: Integration test using private-endpoint / scan
Cross controller integration test using private-endpoint  /  Required Integration Test Status Checks
3s
Cross controller integration test using private-endpoint / Required Integration Test Status Checks
Integration test using private-endpoint  /  Required Integration Test Status Checks
2s
Integration test using private-endpoint / Required Integration Test Status Checks
allure-report  /  Publish Allure report
46s
allure-report / Publish Allure report
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 12 warnings
Runner tests across bases (24.04) / Required Integration Test Status Checks
Process completed with exit code 1.
Integration test using private-endpoint / Required Integration Test Status Checks
Process completed with exit code 1.
integration-tests
The strategy configuration was canceled because "openstack-integration-tests-runner-bases._24_04" failed
Runner tests across bases (24.04) / Plan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan@main. 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/
Runner tests across bases (22.04) / Plan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan@main. 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/
Integration test using private-endpoint / Plan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan@main. 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/
Cross controller integration test using private-endpoint / Plan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan@main. 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/
Runner tests across bases (24.04) / Build charm (github-runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/build@main. 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/
Runner tests across bases (22.04) / Build charm (github-runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/build@main. 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/
Runner tests across bases (24.04) / Plan Image Scanning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan-scan@main. 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/
Runner tests across bases (22.04) / Plan Image Scanning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan-scan@main. 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/
Integration test using private-endpoint / Build charm (github-runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/build@main. 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/
Cross controller integration test using private-endpoint / Build charm (github-runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/build@main. 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/
Integration test using private-endpoint / Plan Image Scanning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan-scan@main. 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/
Cross controller integration test using private-endpoint / Plan Image Scanning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan-scan@main. 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
2026-04-03T06-28-29-896c__build__output__charm__github-runner
56.4 MB
sha256:f4280358e8e5284065a22e1c4f023d803f1b182360320253de6d8c17253f47eb
2026-04-03T06-28-29-896c__plan
298 Bytes
sha256:a11ef435ee9ad3c7247a63ee5438f66ff2046008491e2c6574d3a73cf0b5cb77
2026-04-03T06-28-30-9a73__build__output__charm__github-runner
56.4 MB
sha256:df6d0a57030309b1763ddd178a5d1c86515ff69e5ec1432d0020e2d9b05744b9
2026-04-03T06-28-30-9a73__plan
299 Bytes
sha256:35c01c76db13a21033053a2bf3c9c5b96460ee3806ce73d47c642ffb2cbb6f3e
2026-04-03T06-28-32-9023__build__output__charm__github-runner
56.4 MB
sha256:e37b25feb33815efca3076f79d07ce79c0e03e86a8a9cbd7c84ee4be10d819c3
2026-04-03T06-28-32-9023__plan
299 Bytes
sha256:ddd57c0f6902f501dc2fcd9e2f1d23d17efc65ca19b995225875db1288616ad2
2026-04-03T06-28-32-b7c1__build__output__charm__github-runner
56.4 MB
sha256:b23312410416405732852fbde8cf1c10dd420d40df57208790b40776594d470a
2026-04-03T06-28-32-b7c1__plan
299 Bytes
sha256:058358b2542036aba4954ab5446e2c52af9188aa098bab6dd523800ae787f7bb
allure-fallback-results-17056b4c-c014-4bfb-afd5-d2e826d25788-test_charm_no_runner
1.2 KB
sha256:d04697698674b48158e62c8ec890ad2b45311999cc7fdd04b8b13a82eaa1c378
allure-fallback-results-80221c38-f5a8-4979-b5a9-055e612d547a-test_prometheus_metrics
591 Bytes
sha256:3dcd7c20e20f2b7c6ba7e291fb0d60e327b17791574be644b384161735cc91ca
allure-fallback-results-8686537c-42da-4c85-983a-40aa717220d3-test_charm_upgrade
561 Bytes
sha256:0d6af9770ca853898550023c16f80147ecea35bd33b839e66e68cd236d6eb5a4
allure-fallback-results-a0595d28-9ca3-49ac-8023-daaf44365621-test_multi_unit_same_machine
664 Bytes
sha256:18eb97c669653d82755ad2025c6bf9c06bc65b5aeb9bb220d3afaa2e8d4e13d5
allure-fallback-results-a81293d6-4f21-464d-88b6-8dd89180659f-test_charm_runner
1.83 KB
sha256:cef504e5fb5d2e7e3152e9526c39a80517138ae15293ab9a4105ebea5249ff97
allure-fallback-results-a88fbeea-c98e-4f8d-884a-42b64277eb61-test_charm_fork_path_change
629 Bytes
sha256:26c38e4364a05418ca52dcba5e0308f220380b2a4a33db8b726166cbec212ed6
allure-fallback-results-d0659d16-4c8a-4132-8c15-2f9db59ce214-test_charm_runner
1.83 KB
sha256:ae3477a3e5dd656f07af1eb22ff8b507fcc163f0e734e96beba62bbcbc332cac
allure-results-17056b4c-c014-4bfb-afd5-d2e826d25788-test_charm_no_runner
14.3 KB
sha256:a3e795e455bb2fb2487989a52f76296578e21ab08bcd752ecca5a9e9447ec48c
allure-results-80221c38-f5a8-4979-b5a9-055e612d547a-test_prometheus_metrics
29.5 KB
sha256:a9150c3362293ec3e5612c89a0180cdfcb805a202014c03f291fd89710d494bf
allure-results-8686537c-42da-4c85-983a-40aa717220d3-test_charm_upgrade
10.3 KB
sha256:bd739621669ccf3d0fa7fe0c965f34688234891ad0322ea97db46a27778765cf
allure-results-a0595d28-9ca3-49ac-8023-daaf44365621-test_multi_unit_same_machine
4.38 KB
sha256:0a5b77a622ce6fa4c24f500dc57d71ec7be1c195d3949cc62f897b0d29102dc6
allure-results-a81293d6-4f21-464d-88b6-8dd89180659f-test_charm_runner
73.5 KB
sha256:b625f695056672bcd9cb509fc12d8b98d20e1ed4f94e709c4a7cc47a12223583
allure-results-a88fbeea-c98e-4f8d-884a-42b64277eb61-test_charm_fork_path_change
17.3 KB
sha256:476cc609392a6c95c399912dca5a790cf044b29bb87243ef6711f00df4d6d595
allure-results-d0659d16-4c8a-4132-8c15-2f9db59ce214-test_charm_runner
69.9 KB
sha256:0bc7b9c4240a844a29c5a1d7b97d0d07682a81faa62a2a3c08f0c63ce1b0fff0