Description of problem: nuodb-operator fails to pull the following image from RHCC: registry.access.redhat.com/nuodb/nuodb-ce-operator:0.0.2-1 Version-Release number of selected component (if applicable): How reproducible: Everytime Steps to Reproduce: 1. Browse to OperatorHub in the OCP 4.1 console 2. Select the NuoDB operator 3. Choose "Install" and click through the remaining prompts. Actual results: Expected results: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 12m default-scheduler Successfully assigned nuodb/nuodb-ce-operator-774646d64-zn4jl to ip-10-0-171-43.us-east-2.compute.internal Normal Pulling 10m (x4 over 11m) kubelet, ip-10-0-171-43.us-east-2.compute.internal Pulling image "registry.connect.redhat.com/nuodb/nuodb-ce-operator:0.0.2-1" Warning Failed 10m (x4 over 11m) kubelet, ip-10-0-171-43.us-east-2.compute.internal Failed to pull image "registry.connect.redhat.com/nuodb/nuodb-ce-operator:0.0.2-1": rpc error: code = Unknown desc = Error reading manifest 0.0.2-1 in registry.connect.redhat.com/nuodb/nuodb-ce-operator: manifest unknown: manifest unknown Warning Failed 10m (x4 over 11m) kubelet, ip-10-0-171-43.us-east-2.compute.internal Error: ErrImagePull Normal BackOff 10m (x6 over 11m) kubelet, ip-10-0-171-43.us-east-2.compute.internal Back-off pulling image "registry.connect.redhat.com/nuodb/nuodb-ce-operator:0.0.2-1" Warning Failed 113s (x42 over 11m) kubelet, ip-10-0-171-43.us-east-2.compute.internal Error: ImagePullBackOff Additional info:
It appears that the partner has changed the outbound repository name of their operator project from "nuodb-ce-operator" to "nuodb-operator", while the published CSV metadata still refers to the old repository name. I'm working with the partner and Brian Cook to find a resolution to the issue.
A new version of the NuoDB operator metadata (referring to the latest repo name and image tag) was published to OpenShift OperatorHub. The partner and I have both verified that the operator successfully deploys.