Bug 1529083 - Installer got wrong default crio image
Summary: Installer got wrong default crio image
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.0
Assignee: Giuseppe Scrivano
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-26 09:50 UTC by Gaoyun Pei
Modified: 2018-03-28 14:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-28 14:16:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:16:58 UTC

Description Gaoyun Pei 2017-12-26 09:50:03 UTC
Description of problem:
Enable cri-o used in ocp installation, but without setting the crio system container image, prerequisites.yml playbook failed at the following step:

TASK [container_runtime : Pre-pull CRI-O System Container image] ***************
Tuesday 26 December 2017  02:38:25 +0000 (0:00:00.066)       0:01:55.596 ****** 
fatal: [ec2-34-229-101-102.compute-1.amazonaws.com]: FAILED! => {"changed": false, "cmd": ["atomic", "pull", "--storage", "ostree", "registry.access.redhat.com/openshift3/cri-o:{ucrio_image_name:", "ucri-o,", "ucrio_image_tag:", "u3.9}"], "delta": "0:00:00.721600", "end": "2017-12-25 21:38:27.006384", "msg": "non-zero return code", "rc": 2, "start": "2017-12-25 21:38:26.284784", "stderr": "atomic: unrecognized arguments: ucri-o, ucrio_image_tag: u3.9}\nTry 'atomic --help' for more information.", "stderr_lines": ["atomic: unrecognized arguments: ucri-o, ucrio_image_tag: u3.9}", "Try 'atomic --help' for more information."], "stdout": "", "stdout_lines": []}
fatal: [ec2-34-235-132-115.compute-1.amazonaws.com]: FAILED! => {"changed": false, "cmd": ["atomic", "pull", "--storage", "ostree", "registry.access.redhat.com/openshift3/cri-o:{ucrio_image_name:", "ucri-o,", "ucrio_image_tag:", "u3.9}"], "delta": "0:00:00.809181", "end": "2017-12-25 21:38:27.054238", "msg": "non-zero return code", "rc": 2, "start": "2017-12-25 21:38:26.245057", "stderr": "atomic: unrecognized arguments: ucri-o, ucrio_image_tag: u3.9}\nTry 'atomic --help' for more information.", "stderr_lines": ["atomic: unrecognized arguments: ucri-o, ucrio_image_tag: u3.9}", "Try 'atomic --help' for more information."], "stdout": "", "stdout_lines": []}
        to retry, use: --limit @/home/slave6/workspace/Launch-Environment-Flexy/private-openshift-ansible/playbooks/prerequisites.retry



Version-Release number of the following components:
# git describe
openshift-ansible-3.9.0-0.10.0-58-g88b74bd
ansible-2.4.2.0-1.el7ae.noarch

How reproducible:
Always

Steps to Reproduce:
1.Set openshift_use_crio=true in ansible inventory to install and run cri-o, start running playbook openshift-ansible/playbooks/prerequisites.yml


Actual results:
Installer got l_crio_image as "registry.access.redhat.com/openshift3/cri-o:{ucrio_image_name:", "ucri-o,", "ucrio_image_tag:", "u3.9}"

Expected results:

Additional info:

Comment 1 Giuseppe Scrivano 2018-01-11 09:06:48 UTC
PR:

https://github.com/openshift/openshift-ansible/pull/6682

Comment 3 Gaoyun Pei 2018-01-27 04:12:44 UTC
Verify this bug with openshift-ansible-3.9.0-0.24.0.git.0.735690f.el7.noarch.rpm

Set openshift_use_crio=true to enable cri-o used in ocp installation, run installation playbook, it was trying the correct cri-o image:

TASK [container_runtime : debug] ***********************************************
Saturday 27 January 2018  03:23:36 +0000 (0:00:00.029)       0:02:26.299 ****** 
ok: [ec2-34-238-131-192.compute-1.amazonaws.com] => {
    "l_crio_image": "registry.access.redhat.com/openshift3/cri-o:3.9"
}
ok: [ec2-54-242-179-224.compute-1.amazonaws.com] => {
    "l_crio_image": "registry.access.redhat.com/openshift3/cri-o:3.9"
}

TASK [container_runtime : Pre-pull CRI-O System Container image] ***************
Saturday 27 January 2018  03:23:36 +0000 (0:00:00.065)       0:02:26.364 ****** 
fatal: [ec2-34-238-131-192.compute-1.amazonaws.com]: FAILED! => {"changed": false, "cmd": ["atomic", "pull", "--storage", "ostree", "registry.access.redhat.com/openshift3/cri-o:3.9"], "delta": "0:00:01.999927", "end": "2018-01-26 22:23:38.376191", "msg": "non-zero return code", "rc": 1, ...

Comment 6 errata-xmlrpc 2018-03-28 14:16:17 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:0489


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