feat(github): GitHub App authentication #5548
cbartzintegration_test.yaml
on: pull_request
Cross controller integration test using private-endpoint
/
Plan
11s
Integration test using private-endpoint
/
Plan
16s
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
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
0s
Integration test using private-endpoint
/
Required Integration Test Status Checks
0s
allure-report
/
Publish Allure report
Annotations
24 errors and 14 warnings
|
Integration test using private-endpoint / Build charm (github-runner)
The process '/usr/bin/sudo' failed with exit code 1
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_upgrade)
Process completed with exit code 1.
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_upgrade)
build job Integration test using private-endpoint / Build charm (github-runner) failed with conclusion: failure
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_fork_path_change)
Process completed with exit code 1.
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_fork_path_change)
build job Integration test using private-endpoint / Build charm (github-runner) failed with conclusion: failure
|
|
Runner tests across bases (22.04) / Build charm (github-runner)
Canceling since a higher priority waiting request for integration-tests-774 exists
|
|
Runner tests across bases (22.04) / Build charm (github-runner)
The operation was canceled.
|
|
Runner tests across bases (24.04) / Build charm (github-runner)
Canceling since a higher priority waiting request for integration-tests-774 exists
|
|
Runner tests across bases (24.04) / Build charm (github-runner)
The operation was canceled.
|
|
Runner tests across bases (24.04) / Integration tests / Integration tests (test_charm_runner)
Process completed with exit code 1.
|
|
Runner tests across bases (24.04) / Integration tests / Integration tests (test_charm_runner)
build job Runner tests across bases (24.04) / Build charm (github-runner) failed with conclusion: cancelled
|
|
Runner tests across bases (22.04) / Integration tests / Integration tests (test_charm_runner)
Process completed with exit code 1.
|
|
Runner tests across bases (22.04) / Integration tests / Integration tests (test_charm_runner)
build job Runner tests across bases (22.04) / Build charm (github-runner) failed with conclusion: cancelled
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_no_runner)
Process completed with exit code 1.
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_no_runner)
build job Integration test using private-endpoint / Build charm (github-runner) failed with conclusion: failure
|
|
Cross controller integration test using private-endpoint / Integration tests / Integration tests (test_prometheus_metrics)
Process completed with exit code 1.
|
|
Cross controller integration test using private-endpoint / Integration tests / Integration tests (test_prometheus_metrics)
Process completed with exit code 1.
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_multi_unit_same_machine)
The job has exceeded the maximum execution time of 6h0m0s
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_multi_unit_same_machine)
The operation was canceled.
|
|
integration-tests
Canceling since a higher priority waiting request for integration-tests-774 exists
|
|
integration-tests
Canceling since a higher priority waiting request for integration-tests-774 exists
|
|
integration-tests
Canceling since a higher priority waiting request for integration-tests-774 exists
|
|
integration-tests
Canceling since a higher priority waiting request for integration-tests-774 exists
|
|
integration-tests
Canceling since a higher priority waiting request for integration-tests-774 exists
|
|
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 (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/
|
|
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/
|
|
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 / Integration tests / Integration tests (test_charm_upgrade)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_fork_path_change)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
|
|
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/
|
|
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) / 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) / Integration tests / Integration tests (test_charm_runner)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
|
|
Runner tests across bases (22.04) / Integration tests / Integration tests (test_charm_runner)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
|
|
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_no_runner)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
2026-03-31T08-47-20-8d4a__build__output__charm__github-runner
|
56.4 MB |
sha256:80e9eda8a794e33d2cf2782552f2d10084bea389f9cf24b42a036693951c3177
|
|
|
2026-03-31T08-47-20-8d4a__plan
|
299 Bytes |
sha256:c04e9405b1d59885809ce6f7bc77b03d02211b7fffcf79a3f4c73b0931032896
|
|
|
2026-03-31T08-47-20-ba15__plan
|
299 Bytes |
sha256:eb916ecda792433464ffa24a1cc198c42f1bff543b0bcb84e13b52cbc3d7cc9b
|
|
|
2026-03-31T08-47-23-8d6b__plan
|
299 Bytes |
sha256:769791157017b4e7658f2c6cece350f44cc07bd0bf684b47d072adb50879efc0
|
|
|
2026-03-31T08-47-23-9887__plan
|
299 Bytes |
sha256:f3bddc93e3b36482a50c0471061aab351c66ae11a908aeffc4e51b4c293a29fd
|
|
|
allure-fallback-results-2a7769d7-75f9-478d-8e62-6e56e08c13a4-test_charm_runner
|
1.83 KB |
sha256:7751c5aa546cdcea8bc4d104db92560c8002fef2e70c34891171ec247edcec40
|
|
|
allure-fallback-results-4263e5e6-c845-4abd-bc65-fbc1ec7ee3aa-test_prometheus_metrics
|
590 Bytes |
sha256:e4ba9ba178c0a9853ba4000de81f3ae40310a767f4c37165b327976c9496202f
|
|
|
allure-fallback-results-52668ccc-c2f3-49c9-93b0-7bd41a08db62-test_charm_no_runner
|
1.2 KB |
sha256:ac83b7cf216939e1a277a8b9dfdc5e2f9725755ecf14741b882e434711852235
|
|
|
allure-fallback-results-68ea8726-4983-43cb-a73b-5da421290f67-test_charm_upgrade
|
563 Bytes |
sha256:d8eda6b4deac7bade6a0cb8437ef209836f913654435dd132661a4448988eec4
|
|
|
allure-fallback-results-abd8ed3f-cddb-4fa3-8bb8-45724d608d1f-test_multi_unit_same_machine
|
662 Bytes |
sha256:cc58cc322e0f19cf57f7d5d3e028725c632b9d2f701bd46f83518d126cc3ee76
|
|
|
allure-fallback-results-cf1eeb5d-a741-4872-b139-6d51f8410870-test_charm_fork_path_change
|
628 Bytes |
sha256:ef553ee298e1a0d649436bb989f8ed3dedc8a5abfb0e0d49ae907f57e99d8d6d
|
|
|
allure-fallback-results-fa8ec5fb-9aae-4b81-84b1-285c1b8eb20d-test_charm_runner
|
1.83 KB |
sha256:28cc4d129a93690cd45d2eb947c06b15b4de1e8482e449096f6b759e12a43f4a
|
|
|
allure-results-4263e5e6-c845-4abd-bc65-fbc1ec7ee3aa-test_prometheus_metrics
|
16.3 KB |
sha256:6b9645e043448a7d8cbd698edce9e5da2fe9558dfda6c16d5bc2f16e270f54bf
|
|