Bug 1744314 - Metering operator is calling a dated 'oauth-proxy' image
Summary: Metering operator is calling a dated 'oauth-proxy' image
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Metering Operator
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.0
Assignee: Chance Zibolski
QA Contact: Peter Ruan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-21 19:46 UTC by Peter Ruan
Modified: 2019-08-26 22:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-26 22:51:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github operator-framework operator-metering pull 911 0 None None None 2019-08-23 22:36:46 UTC

Description Peter Ruan 2019-08-21 19:46:20 UTC 
Description of problem:
  The oauth-proxy image being used by metering is dated, ImagePullBackOff
  Normal   Pulling           29s (x2 over 2m43s)  kubelet, qe-sharedenv-8201-88bcz-compute-0  Pulling image "openshift/oauth-proxy:v1.1.0"

  We should be using 4.x image.

Version-Release number of selected component (if applicable):

4.x
How reproducible:

always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Peter Ruan 2019-08-26 22:47:21 UTC 
verified that PR https://github.com/operator-framework/operator-metering/pull/911 fixed the issue.

NAME                                  READY   STATUS    RESTARTS   AGE
hdfs-datanode-0                       1/1     Running   0          4m40s
hdfs-namenode-0                       1/1     Running   0          4m40s
hive-metastore-0                      2/2     Running   0          4m16s
hive-server-0                         3/3     Running   0          4m16s
metering-operator-7977cbbdc4-k4vwt    2/2     Running   0          6m28s
presto-coordinator-0                  2/2     Running   0          3m46s
reporting-operator-6675457555-dlzzg   2/2     Running   0          3m10s
Note You need to log in before you can comment on or make changes to this bug.