Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1541041 - [3.7] Provisioner pod fails to deploy becasue of incorrect image prefix
[3.7] Provisioner pod fails to deploy becasue of incorrect image prefix
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity high
: ---
: 3.7.z
Assigned To: Vadim Rutkovsky
Gaoyun Pei
:
Depends On: 1523534
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-01 10:10 EST by Scott Dodson
Modified: 2018-04-05 05:37 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1523534
Environment:
Last Closed: 2018-04-05 05:37:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:37 EDT

  None (edit)
Description Scott Dodson 2018-02-01 10:10:49 EST
+++ 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 10:11:45 EST
Created https://github.com/openshift/openshift-ansible/pull/6948 for 3.7 branch
Comment 2 Vadim Rutkovsky 2018-02-08 04:54:00 EST
Fix is available in openshift-ansible-3.7.29-1.git.0.e1bfc35.el7
Comment 3 Gaoyun Pei 2018-02-10 00:21:05 EST
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 05:37:08 EDT
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

Note You need to log in before you can comment on or make changes to this bug.