Bug 1812036

Summary: ose-ansible image has Ansible 2.6 installed
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: ReleaseAssignee: Luke Meyer <lmeyer>
Status: CLOSED ERRATA QA Contact: Gaoyun Pei <gpei>
Severity: high Docs Contact:
Priority: high    
Version: 3.11.0CC: aanjarle, aos-bugs, dconsoli, gpei, jdelft, joboyer, jokerman, lmeyer, openshift-bugs-escalate, rteague
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-17 20:21:27 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:

Description Scott Dodson 2020-03-10 12:15:01 UTC
We should bump the image to include the ansible 2.8 repos.

Comment 1 Russell Teague 2020-03-10 15:56:34 UTC
I pulled the image and saw it was installed from repo rhel-7-server-ansible-2.6-rpms.  This does not look like a configuration in openshift-ansible.  Any ideas on where/how that repo is set when building the image?

Dep-Install ansible-2.6.20-1.el7ae.noarch                                   @rhel-7-server-ansible-2.6-rpms

Comment 2 Russell Teague 2020-05-13 17:50:18 UTC
This bug is not scheduled for the current sprint.

Comment 6 Russell Teague 2020-05-18 19:06:26 UTC
PR submitted.

Comment 7 Russell Teague 2020-05-18 19:15:05 UTC
I'm moving this to ART to get their help with merging the PR.  I want to make sure it goes through their defined workflow.  My PR can be closed and another one opened if that makes it easier.

Comment 19 Gaoyun Pei 2020-06-10 06:09:15 UTC
# docker run --entrypoint rpm registry-proxy.engineering.redhat.com/rh-osbs/openshift3-ose-ansible:v3.11.232 -q ansible
ansible-2.8.12-1.el7ae.noarch

Comment 21 errata-xmlrpc 2020-06-17 20:21:27 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-2020:2477