The credential content in "Openshift Object YAML" is not merged in merge-registry-credentials step

[jinhli]

Bug Description

pr: redhat-openshift-ecosystem/certified-operators#538
Project: 61af7b43b1610a914eccb3f3

If the external private registry is used in the operator, though the credential is added to "OpenShift Object YAML" field on the connect Project settings page, it is not merged in merge-registry-credentials step.
In the pipeline.log, there is an message “[merge-registry-credentials : get-and-decrypt-project-tokens] No partner's registry token has been provided.”
pipeline-from mantaflow.txt

Steps to Reproduce:

1. Add credential content to "OpenShift Object YAML" field on the Project settings page
2. Submit the pr via the hosted pipeline, the pr failed with "verify-ci-result"
3. Operator could not be deployed via OLM, there is error "ImagePullBackOff” in deployment pod.

Expected Result

The operand image could be pulled

Actual Result

The container could not be pulled due to "ImagePullBackOff”

Additional Context

Manually add the credential of the registry, the image could be pulled

1.Create a regcred.yml with the credentials provided by Partner
2.OC login to the cluster and choose the project which the operator installed
3.Create a secret in cluster “oc apply -f regcred.yml” in the project
4.Check the secret has been added “oc get secret”
5.Add image pull secret to service account
oc patch serviceaccount mantaflow-operator-controller-manager -p '{"imagePullSecrets": [{"name": "registry-dockerconfig-secret"}]}'
6.go to the "deployment", delete the pod, it will create a new pod to apply the change, and the operator could be installed successfully.

[jinhli]

hi, does anyone take a look at this issue?

[jpaulovic]

Should this be closed?

[jinhli]

I did not get any support case for this issue any more. And I saw the sub-issue of it has been fixed, I think it could be closed, but still need @tonytcampbell final confirmation.