When running the fpdc playbook to deploy the application in production, I have the following error.
fatal: [os-master01.phx2.fedoraproject.org]: FAILED! => {"changed": true, "cmd": "oc -n fpdc rollout latest fpdc", "delta": "0:00:00.348141", "end": "2018-11-13 07:10:33.904146", "msg": "non-zero return code", "rc": 1, "start": "2018-11-13 07:10:33.556005", "stderr": "Error from server (BadRequest): cannot trigger a deployment for \"fpdc\" because it contains unresolved images", "stderr_lines": ["Error from server (BadRequest): cannot trigger a deployment for \"fpdc\" because it contains unresolved images"], "stdout": "", "stdout_lines": []}
fpdc is using the s2i python image available in openshift catalog.
Note that this is working in staging
When do you need this? (YYYY/MM/DD)
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
Metadata Update from @bowlofeggs: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: OpenShift
Fixed.
openshift had cached registry.redhat.io, but thats a akami ip and apparently it got used by some other place.
I did a pkill -HUP dnsmasq and it flushed out all its caches.
It now built and deployed.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.