Description of problem: Back-off pulling image "registry.connect.redhat.com/turbonomic/kubeturbo-operator@sha256:6ff2f2dc6ca50fceef1ffc40d6c40aa965fb40df3d6f0e357c4292d54fb36413" Version-Release number of selected component (if applicable): OCP Version: 4.7.0-0.nightly-2021-02-18-110409 Red Hat Integration - Camel K Version: 1.2.1 How reproducible: Always Steps to Reproduce: 1.Install the Operator using the Operator Hub
Can't reproduce bug. I was able to fully install the operator. Same version (1.2.1) on OCP 4.7.0 GA oc get events 6m44s Normal RequirementsUnknown clusterserviceversion/red-hat-camel-k-operator.v1.2.1 requirements not yet checked 6m44s Normal RequirementsNotMet clusterserviceversion/red-hat-camel-k-operator.v1.2.1 one or more requirements couldn't be found 6m42s Normal AllRequirementsMet clusterserviceversion/red-hat-camel-k-operator.v1.2.1 all requirements found, attempting install 6m42s Normal InstallSucceeded clusterserviceversion/red-hat-camel-k-operator.v1.2.1 waiting for install components to report healthy 6m42s Normal InstallWaiting clusterserviceversion/red-hat-camel-k-operator.v1.2.1 installing: waiting for deployment camel-k-operator to become ready: Waiting for deployment spec update to be observed... 6m42s Normal InstallWaiting clusterserviceversion/red-hat-camel-k-operator.v1.2.1 installing: waiting for deployment camel-k-operator to become ready: Waiting for rollout to finish: 0 of 1 updated replicas are available... 6m16s Normal InstallSucceeded clusterserviceversion/red-hat-camel-k-operator.v1.2.1 install strategy completed with no errors 6m9s Normal KameletConditionChanged kamelet/salesforce-source Condition "Ready" is "True" for Kamelet salesforce-source 6m9s Normal KameletPhaseUpdated kamelet/salesforce-source Kamelet salesforce-source in phase "Ready" 6m9s Normal KameletConditionChanged kamelet/slack-source Condition "Ready" is "True" for Kamelet slack-source 6m9s Normal KameletPhaseUpdated kamelet/slack-source Kamelet slack-source in phase "Ready" 6m9s Normal KameletConditionChanged kamelet/telegram-source Condition "Ready" is "True" for Kamelet telegram-source 6m9s Normal KameletPhaseUpdated kamelet/telegram-source Kamelet telegram-source in phase "Ready" oc get pods NAME READY STATUS RESTARTS AGE camel-k-kit-c0ulbtmhflgimnflhng0-1-build 0/1 Completed 0 4m22s camel-k-operator-7645f46567-gn5q7 1/1 Running 0 9m1s example-58c6fdf49b-xcj7j 1/1 Running 0 3m31s oc get operators NAME AGE red-hat-camel-k.default 9m54s oc describe operators (...) Conditions: Last Transition Time: 2021-03-01T20:57:36Z Last Update Time: 2021-03-01T20:57:36Z Message: install strategy completed with no errors Reason: InstallSucceeded Status: True Type: Succeeded Kind: ClusterServiceVersion Name: red-hat-camel-k-operator.v1.2.1 Namespace: default API Version: operators.coreos.com/v1 Kind: OperatorCondition Name: red-hat-camel-k-operator.v1.2.1 Namespace: default Deployed one sample of the integration API with success as well: oc get integration NAME PHASE KIT REPLICAS example Running kit-c0ulbtmhflgimnflhng0 1 STEPS: 1) Select the operator on the UI 2) Click install 3) Choose only one namespace 4) Pick the default namespace 5) Run the install
although it is marked as 4.8, I test it on 4.7 because no fix for it. -- [root@preserve-olm-env 1929335]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2021-02-26-160517 True False 5m44s Cluster version is 4.7.0-0.nightly-2021-02-26-160517 [root@preserve-olm-env 1929335]# 1, install it using the Operator Hub 2, it succeds. --
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438