Allure Report #351
swetha1654allure-report.yaml
on: schedule
Matrix: integration-tests
allure-report
/
Publish Allure report
1m 14s
Annotations
7 errors and 16 warnings
|
integration-tests (dns-policy-operator) / Integration tests / Integration tests
Process completed with exit code 1.
|
|
integration-tests (dns-policy-operator) / Integration tests / Integration tests
Process completed with exit code 1.
|
|
integration-tests (dns-policy-operator) / Required Integration Test Status Checks
Process completed with exit code 1.
|
|
integration-tests (bind-operator) / Integration tests / Integration tests
Process completed with exit code 1.
|
|
integration-tests (bind-operator) / Integration tests / Integration tests
Process completed with exit code 1.
|
|
Allure Report
The strategy configuration was canceled because "integration-tests.dns-policy-operator" failed
|
|
Allure Report
The strategy configuration was canceled because "integration-tests.dns-policy-operator" failed
|
|
integration-tests (bind-operator) / 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-tests (dns-policy-operator) / 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-tests (dns-secondary-operator) / 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-tests (dns-integrator-operator) / 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-tests (bind-operator) / Build charm (bind)
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-tests (bind-operator) / 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-tests (dns-integrator-operator) / Build charm (dns-integrator)
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-tests (dns-integrator-operator) / 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-tests (dns-integrator-operator) / Integration tests / Integration tests
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-integration@main, charmed-kubernetes/actions-operator@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-tests (dns-policy-operator) / Build charm (dns-policy)
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-tests (dns-policy-operator) / 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-tests (dns-secondary-operator) / Build charm (dns-secondary)
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-tests (dns-secondary-operator) / 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-tests (dns-policy-operator) / Integration tests / Integration tests
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-integration@main, charmed-kubernetes/actions-operator@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-tests (bind-operator) / Integration tests / Integration tests
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-integration@main, charmed-kubernetes/actions-operator@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-tests (dns-secondary-operator) / Integration tests / Integration tests
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-integration@main, charmed-kubernetes/actions-operator@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-05-13T07-10-19-9504__bind-operator__build__output__charm__bind
|
9.72 MB |
sha256:86fc16ba4da4bb626801e3a10879ae9b81e10e1053662f357ba8e83feca5e5c8
|
|
|
2026-05-13T07-10-19-9504__bind-operator__plan
|
307 Bytes |
sha256:da45564eb496a0e8bd304437afcabce69a7e092a7945b6f23875117256d09380
|
|
|
2026-05-13T07-10-22-8ce6__dns-secondary-operator__build__output__charm__dns-secondary
|
12.4 MB |
sha256:47773f2cdbe9803b032ccc234f6e1dbd627b66743c16441f4c3b6e223b203862
|
|
|
2026-05-13T07-10-22-8ce6__dns-secondary-operator__plan
|
311 Bytes |
sha256:ebbe0456c03f7a9d7a29f78ab4a071bd360c04868bdafd046a31dd8d04f0913c
|
|
|
2026-05-13T07-10-22-b612__dns-policy-operator__build__output__charm__dns-policy
|
10.5 MB |
sha256:45b9237e0115829da2246c8ebd014b397ee8a526860942b8e2710f0f8f8a1709
|
|
|
2026-05-13T07-10-22-b612__dns-policy-operator__plan
|
308 Bytes |
sha256:98e57e657e0a0d42fcf5791d4145f20470917241243847c1fe54e02635689573
|
|
|
2026-05-13T07-10-27-b978__dns-integrator-operator__build__output__charm__dns-integrator
|
9.67 MB |
sha256:6d86dedc461de00dcc2000b25c6539b5666d60c4089258cce169db7c51b29a51
|
|
|
2026-05-13T07-10-27-b978__dns-integrator-operator__plan
|
315 Bytes |
sha256:34f37a257bbbdf7cd54b2cf58e31a403301fe16e933a761c8002e06caf701c48
|
|
|
allure-fallback-results-75462943-9d0c-4bcc-80f1-d9bb0f6f3968
|
555 Bytes |
sha256:f1377cd5646ffacde18c2968bc89a53a202b5af7b46c25023eec93b3cd44eb84
|
|
|
allure-fallback-results-b03abb9d-b683-420e-9e60-5411e088a3ba
|
483 Bytes |
sha256:74b3c05ffd6c3fccdeb40492bd2c92a2a62845a8abc9027d21f9ae27d91f8ae6
|
|
|
allure-fallback-results-d00ebd71-6b94-425e-87c7-03465ce5a34f
|
5.02 KB |
sha256:a75299d9fdaba9bae3b0d7fa322a5dfd92efb5cdebcb02a62c2e8d6e3c6cb470
|
|
|
allure-fallback-results-e2299036-68cb-477d-a704-b892cafdfd13
|
579 Bytes |
sha256:1e30bde3008529fa38d949196c6844592e3c13f2e82458d3b07bd94ccda377a1
|
|
|
allure-results-75462943-9d0c-4bcc-80f1-d9bb0f6f3968
|
5.85 KB |
sha256:7f04f91f1369d444b6e5cb673be2c54123589f5604175eee519acf34f7cbd73b
|
|
|
allure-results-b03abb9d-b683-420e-9e60-5411e088a3ba
|
911 Bytes |
sha256:e1922eb625d8ec6a072ea06a817781e5fe2cb41aa7ae948415cdec14a1e3f5e6
|
|
|
allure-results-d00ebd71-6b94-425e-87c7-03465ce5a34f
|
21.4 KB |
sha256:74ec764ffcd5d6e4c92b472775c5aeea21ff93ba541ae144dba1655cc50ab381
|
|
|
allure-results-e2299036-68cb-477d-a704-b892cafdfd13
|
5.68 KB |
sha256:334a5385d3def5d9155745e2dea27f8f9d1707a45efca724d34bea70125df4a9
|
|