Skip to content

integration-tests #5567

integration-tests

integration-tests #5567

Triggered via schedule April 2, 2026 18:19
Status Failure
Total duration 39m 51s
Artifacts 22

integration_test.yaml

on: schedule
Cross controller integration test using private-endpoint  /  Plan
9s
Cross controller integration test using private-endpoint / Plan
Integration test using private-endpoint  /  Plan
9s
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
4s
Cross controller integration test using private-endpoint / Plan Image Scanning
Integration test using private-endpoint  /  Plan Image Scanning
3s
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
2s
Cross controller integration test using private-endpoint / Required Integration Test Status Checks
Integration test using private-endpoint  /  Required Integration Test Status Checks
3s
Integration test using private-endpoint / Required Integration Test Status Checks
allure-report  /  Publish Allure report
56s
allure-report / Publish Allure report
Fit to window
Zoom out
Zoom in

Annotations

16 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
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) / 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/
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 (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/
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 (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/
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/
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/
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/

Artifacts

Produced during runtime
Name Size Digest
2026-04-02T18-19-33-9bac__build__output__charm__github-runner
56.4 MB
sha256:f15f885cc83159654608cded9da1e9e45fd8c2e6274a6a9a0fdb1b815536bb63
2026-04-02T18-19-33-9bac__plan
299 Bytes
sha256:5a5dfa11745d8d049bf5798214f472e899fe75c0bd5ce3050561ecaff5b0a755
2026-04-02T18-19-33-9f1b__build__output__charm__github-runner
56.4 MB
sha256:268573bfe8747760db148802c4b5f057f901a5aa2832b4680b00208f74734a46
2026-04-02T18-19-33-9f1b__plan
299 Bytes
sha256:baff10ec17771227fadd061d8e5faa30d45b3babdce114c2213bd99b7d26a2e8
2026-04-02T18-19-33-aa72__build__output__charm__github-runner
56.4 MB
sha256:b59c102ea8cbb1a7000d70ac6c5dcbec485972084ca67367ed85c0c334a7ef94
2026-04-02T18-19-33-aa72__plan
299 Bytes
sha256:2a7240d08b604685c05fa4ca43c028f16c15e8bcf3c1696cf20244c9f24d3245
2026-04-02T18-19-33-ae0e__build__output__charm__github-runner
56.4 MB
sha256:81d389c3e81963e60748a70a08e86eeb03fe9b2bbc24c787394f0cdcf5d3508d
2026-04-02T18-19-33-ae0e__plan
299 Bytes
sha256:651175fe7c52a6cfe8779e3cfd3fca8cdaf260752d7e2bf008cc5cdd041d5629
allure-fallback-results-0498533a-3814-4f05-9271-54839dbd7007-test_charm_upgrade
563 Bytes
sha256:c04e343ee18804d0e26aebd3399453723505b7de0d77cc8981c54234500bc56c
allure-fallback-results-0d06728a-3adb-45c6-8b2b-e940762120e0-test_charm_no_runner
1.2 KB
sha256:75f484ad20416c5727db6a5787b43864cdcce6632d46cf05ccb28ff04032f820
allure-fallback-results-3502263c-9c15-4450-9a34-02efcaaa42cb-test_prometheus_metrics
591 Bytes
sha256:08cef916c2940bb00920f06eed6d617fc6b2cff51df01542a9c0a665876a1cc1
allure-fallback-results-4f898898-9011-4f5f-8ca9-447670eb1753-test_charm_runner
1.83 KB
sha256:ac147e86b6ea9e1878c553cc9a1a02491c8b63fe95a1f0cd9edf72a7f3dced8c
allure-fallback-results-a2a4e2c9-3a62-485f-9447-b72b0ab59244-test_multi_unit_same_machine
666 Bytes
sha256:73bc84306d991754f2785320637001842a52388f1c1a52921cbd831f6b29d09e
allure-fallback-results-c5c102fa-6d4b-4258-a5fc-a802dc3f07c1-test_charm_runner
1.83 KB
sha256:1d03ef289a4a9db8c4907b35c5fe7680dc22050f780df6ef75df0acdcd95a103
allure-fallback-results-d50bc134-9705-4eb8-bb5e-ef81c653c8f8-test_charm_fork_path_change
629 Bytes
sha256:80e7f7a959b22d8ea50c0b108d333ff71639e690e74f13e4fc943326cc875f1b
allure-results-0498533a-3814-4f05-9271-54839dbd7007-test_charm_upgrade
10.3 KB
sha256:730de7bfa27721326caf6312a4a82709d0d60e3a667d9a3b260846924c722bce
allure-results-0d06728a-3adb-45c6-8b2b-e940762120e0-test_charm_no_runner
18.5 KB
sha256:41d575c76873758924b629136f03c6a2a58dd2e00457e034f6a9e5d8f7d8a768
allure-results-3502263c-9c15-4450-9a34-02efcaaa42cb-test_prometheus_metrics
17.5 KB
sha256:1dfded85ad595b960271d23c8e990b9ac269277cfa7efa46b4131e102b14354b
allure-results-4f898898-9011-4f5f-8ca9-447670eb1753-test_charm_runner
21.2 KB
sha256:a46e029751e8e53962730a222fc754f2de8c1569fc3da66c54b6435fec67d936
allure-results-a2a4e2c9-3a62-485f-9447-b72b0ab59244-test_multi_unit_same_machine
13.1 KB
sha256:d45c6a170cae6b3f7f842a53e17f7f95799521f558df32993c2ff4ba0014fd98
allure-results-c5c102fa-6d4b-4258-a5fc-a802dc3f07c1-test_charm_runner
30.5 KB
sha256:b313394a4f3ec7f6788e9e3197324c0402b5db96b8fb9c14953a3ee2e83f636f
allure-results-d50bc134-9705-4eb8-bb5e-ef81c653c8f8-test_charm_fork_path_change
47.3 KB
sha256:81f13f101409bbdaf91d0d941a6c13df690b446ede643c4c3c211846fdf84483