Bug 1646844 - Autoheal deployment should use the oauth-proxy image shipped with OpenShift
Summary: Autoheal deployment should use the oauth-proxy image shipped with OpenShift
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.z
Assignee: Scott Dodson
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-06 06:47 UTC by Gaoyun Pei
Modified: 2019-02-15 21:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-15 21:21:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gaoyun Pei 2018-11-06 06:47:51 UTC
Description of problem:
oauth-proxy image used for openshift_autoheal deployment is hard coded as 
image: openshift/oauth-proxy:v1.1.0
https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/openshift_autoheal/files/template.yml#L147

Actually we should use the oauth-proxy image shipped with openshift
openshift3/oauth-proxy:v3.11



Version-Release number of the following components:
$ git describe
openshift-ansible-3.11.39-1-2-gbf92f9c


How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

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

Comment 1 Scott Dodson 2018-11-06 19:14:52 UTC
Doesn't actually require knowledge of autoheal internals, we can take this on in Installer component. Just needs to have the image spec templated.

Comment 2 Scott Dodson 2019-02-15 21:21:02 UTC
There appear to be no active cases related to this bug. As such we're closing this bug in order to focus on bugs that are still tied to active customer cases. Please re-open this bug if you feel it was closed in error or a new active case is attached.


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