Wait a while for OpenShift API server to apply last changes (#710) #2873
main.yml
on: push
Operator Linting
58s
stf-run-ci Linting
57s
Check if generating the bundle would result in local changes
6s
Build Operator check
57s
Build bundle check
52s
Validate the generated bundle and perform scorecard checks
59s
Annotations
26 warnings
|
Check if generating the bundle would result in local changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.3. 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/
|
|
Build bundle check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.3. 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/
|
|
Operator Linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.3, actions/setup-python@v5. 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/
|
|
fqcn[action-core]:
roles/servicetelemetry/tasks/base_smartgateway.yml#L2
Use FQCN for builtin module actions (set_fact).
|
|
schema[meta]:
roles/servicetelemetry/meta/main.yml#L1
$.galaxy_info.min_ansible_version 2.9 is not of type 'string'. See https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html#using-role-dependencies
|
|
var-naming[no-role-prefix]:
roles/servicetelemetry/defaults/main.yml#L149
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: smartgateway_deployment_size)
|
|
var-naming[no-role-prefix]:
roles/servicetelemetry/defaults/main.yml#L146
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: _ephemeral_storage_enabled)
|
|
var-naming[no-role-prefix]:
roles/servicetelemetry/defaults/main.yml#L144
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: is_openshift)
|
|
var-naming[no-role-prefix]:
roles/servicetelemetry/defaults/main.yml#L143
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: is_k8s)
|
|
stf-run-ci Linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.3, actions/setup-python@v5. 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/
|
|
var-naming[no-role-prefix]:
roles/servicetelemetry/defaults/main.yml#L10
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: prometheus_operator_label)
|
|
name[template]:
build/stf-run-ci/tasks/clone_repos.yml#L81
Jinja templates should only be at the end of 'name'
|
|
var-naming[no-role-prefix]:
roles/servicetelemetry/defaults/main.yml#L9
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: prometheus_operator_api_string)
|
|
name[template]:
build/stf-run-ci/tasks/clone_repos.yml#L67
Jinja templates should only be at the end of 'name'
|
|
name[template]:
build/stf-run-ci/tasks/clone_repos.yml#L61
Jinja templates should only be at the end of 'name'
|
|
var-naming[no-role-prefix]:
roles/servicetelemetry/defaults/main.yml#L6
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: observability_strategy)
|
|
name[template]:
build/stf-run-ci/tasks/clone_repos.yml#L47
Jinja templates should only be at the end of 'name'
|
|
var-naming[no-role-prefix]:
roles/servicetelemetry/defaults/main.yml#L5
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: clouds_remove_on_missing)
|
|
name[template]:
build/stf-run-ci/tasks/clone_repos.yml#L41
Jinja templates should only be at the end of 'name'
|
|
name[template]:
build/stf-run-ci/tasks/clone_repos.yml#L27
Jinja templates should only be at the end of 'name'
|
|
name[template]:
build/stf-run-ci/tasks/clone_repos.yml#L21
Jinja templates should only be at the end of 'name'
|
|
name[template]:
build/stf-run-ci/tasks/clone_repos.yml#L7
Jinja templates should only be at the end of 'name'
|
|
yaml[new-line-at-end-of-file]:
build/stf-run-ci/handlers/main.yml#L2
No new line character at the end of file
|
|
var-naming[no-reserved]:
build/stf-run-ci/defaults/main.yml#L55
Variables names must not be Ansible reserved names. (namespace) (vars: namespace)
|
|
Build Operator check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.3. 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/
|
|
Validate the generated bundle and perform scorecard checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.3, helm/kind-action@v1.10.0. 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/
|