Closed johnkim76 closed 7 years ago
Can you paste the logs from the broker?
I suspect this is a configuration issue and not actually a bug in the broker. Can you oc exec
into a broker container that you think is not honoring the pull policy and post the /etc/ansible-service-broker/config.yaml
contents?
Are you deploying with catasb? Which branch and environment?
@rthallisey @eriknelson I was trying to debug another issue, and with @jwmatthews help, we determined that the pull policy was being set to 'always'. I'm using catasb (dev branch), and I've been deleting all the images before doing a reset of the environment. Currenlty in a modified environment to complete another task, but I'll provide the requested info once I reset it back.
@johnkim76 Are you using the release-0.9 broker or the master broker?
@eriknelson I was using catasb which seemed to pull the latest image. I was not using the broker source when I hit this issue.
I can't reproduce with latest deployment from catasb 'dev' branch.
$ oc export pod apb-4a477dee-ee0d-4524-8c6d-dbbed6ddca04 apiVersion: v1 kind: Pod metadata: annotations: openshift.io/scc: anyuid creationTimestamp: null name: apb-4a477dee-ee0d-4524-8c6d-dbbed6ddca04 spec: containers:
@jwmatthews @eriknelson @rthallisey I just reset everything, and I can NOT reproduce this either.
cannot reproduce.. closing.
The configurable pull policy is currently being set to 'Always', even though it's being configured to be set to "IfNotPresent".