Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1541041

Summary:	[3.7] Provisioner pod fails to deploy becasue of incorrect image prefix
Product:	OpenShift Container Platform	Reporter:	Scott Dodson <sdodson>
Component:	Installer	Assignee:	Vadim Rutkovsky <vrutkovs>
Status:	CLOSED ERRATA	QA Contact:	Gaoyun Pei <gpei>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.0	CC:	aos-bugs, dmoessne, jialiu, jkaur, jokerman, mmccomas, vrutkovs
Target Milestone:	---
Target Release:	3.7.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1523534	Environment:
Last Closed:	2018-04-05 09:37:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1523534
Bug Blocks:

Description Scott Dodson 2018-02-01 15:10:49 UTC

+++ This bug was initially created as a clone of Bug #1523534 +++

Description of problem:  Provisioner pod fails to deploy becasue of incorrect image prefix


oc logs provisioners-efs-1-rw74p -n openshift-infra

Error from server (BadRequest): container "efs-provisioner" in pod "provisioners-efs-1-rw74p" is waiting to start: trying and failing to pull image
Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results: Fails to pull image for efs-provisioner

Expected results: It should start without issue

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

--- Additional comment from Jaspreet Kaur on 2017-12-08 04:28:46 EST ---

PR : https://github.com/openshift/openshift-ansible/pull/6397

PR : https://github.com/openshift/openshift-ansible/pull/6396

--- Additional comment from Scott Dodson on 2018-01-19 15:04:12 EST ---

Vadim can you run with your comment on https://github.com/openshift/openshift-ansible/pull/6396#issuecomment-358295687

Lets make sure that we fix this first on master and then get release-3.7 and release-3.6 fixed.

--- Additional comment from Vadim Rutkovsky on 2018-01-25 09:11:59 EST ---

Created https://github.com/openshift/openshift-ansible/pull/6868

--- Additional comment from Vadim Rutkovsky on 2018-01-31 04:51:35 EST ---

Created https://github.com/openshift/openshift-ansible/pull/6948 for 3.7 branch

Comment 1 Scott Dodson 2018-02-01 15:11:45 UTC

Created https://github.com/openshift/openshift-ansible/pull/6948 for 3.7 branch

Comment 2 Vadim Rutkovsky 2018-02-08 09:54:00 UTC

Fix is available in openshift-ansible-3.7.29-1.git.0.e1bfc35.el7

Comment 3 Gaoyun Pei 2018-02-10 05:21:05 UTC

Verify this bug with openshift-ansible-3.7.29-1.git.0.e1bfc35.el7.noarch.rpm

When openshift_provisioners_image_prefix not set in ansible inventory, run playbooks/byo/openshift-cluster/openshift-provisioners.yml, it got correct openshift_provisioners_image_prefix and openshift_provisioners_image_version.


TASK [openshift_provisioners : Set eventrouter image facts] ************************************************************************************************************
ok: [ec2-54-86-22-220.compute-1.amazonaws.com] => {"ansible_facts": {"openshift_provisioners_image_prefix": "registry.access.redhat.com/openshift3/", "openshift_provisioners_image_version": "v3.7.29"}, "changed": false}

Comment 7 errata-xmlrpc 2018-04-05 09:37:08 UTC

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, 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/RHBA-2018:0636