found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

found status KeycloakStatusCondition{type='Ready', status=True, message=''} and expected status false

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@96202dee4ae1c2f46a62fe197273aaf22b83f42d, redhat-actions/openshift-tools-installer@144527c7d98999f2652264c048c7a9bd103f8a82. 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/

Failed to cache opm 4.16.4: ReserveCacheError: Unable to reserve cache with key opm_4.16.4_linux_amd64, another job may be creating this cache.

Failed to check cache for opm 4.16.4: Error: Cache service responded with 400

Failed to cache oc 4.21.16: ReserveCacheError: Unable to reserve cache with key oc_4.21.16_linux_amd64, another job may be creating this cache.

Failed to check cache for oc 4.21.16: Error: Cache service responded with 400

Multiple files were found for oc that matched the current OS and architecture: openshift-client-linux-4.21.16.tar.gz, openshift-client-linux-amd64-rhel8-4.21.16.tar.gz, openshift-client-linux-amd64-rhel9-4.21.16.tar.gz, openshift-client-linux-arm64-4.21.16.tar.gz, openshift-client-linux-arm64-rhel8-4.21.16.tar.gz, openshift-client-linux-arm64-rhel9-4.21.16.tar.gz, openshift-client-linux-ppc64le-4.21.16.tar.gz, openshift-client-linux-ppc64le-rhel8-4.21.16.tar.gz, openshift-client-linux-ppc64le-rhel9-4.21.16.tar.gz, openshift-client-linux-s390x-rhel8-4.21.16.tar.gz, openshift-client-linux-s390x-rhel9-4.21.16.tar.gz. Selecting the first one.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@96202dee4ae1c2f46a62fe197273aaf22b83f42d. 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/