Bug 1688519

Summary: UPGRADE service-ca operator not reporting payload version
Product: OpenShift Container Platform Reporter: Derek Carr <decarr>
Component: apiserver-authAssignee: Sally <somalley>
Status: CLOSED ERRATA QA Contact: Chuan Yu <chuyu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, nagrawal, sponnaga
Target Milestone: ---Keywords: BetaBlocker
Target Release: 4.1.0   
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: 2019-06-04 10:45:47 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 Derek Carr 2019-03-13 21:54:46 UTC 
Description of problem:
service-ca operator not reporting clusteroperator version

Version-Release number of selected component (if applicable):
4.0.0-0.alpha-2019-03-13-010143

How reproducible:
Always

Actual results:
oc get clusteroperators service-ca
NAME                       VERSION   AVAILABLE   PROGRESSING   FAILING   SINCE
service-ca             False       False         True      14h


Expected results:
Version reports the payload version when it achieves level.
Comment 1 Sally 2019-03-18 18:18:05 UTC 
https://github.com/openshift/service-ca-operator/pull/34
Comment 3 Chuan Yu 2019-03-22 06:06:23 UTC 
Verified.

$ oc get clusteroperator service-ca
NAME         VERSION                             AVAILABLE   PROGRESSING   FAILING   SINCE
service-ca   4.0.0-0.nightly-2019-03-22-032251   True        False         False     14m

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.0.0-0.nightly-2019-03-22-032251   True        False         23s     Cluster version is 4.0.0-0.nightly-2019-03-22-032251
Comment 5 errata-xmlrpc 2019-06-04 10:45:47 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-2019:0758