Bug 1812047 - The Upgradeable status of "service-catalog-apiserver" is "Unknown" before enable it
Summary: The Upgradeable status of "service-catalog-apiserver" is "Unknown" before ena...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Catalog
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.5.0
Assignee: Jesus M. Rodriguez
QA Contact: Fan Jia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-10 12:34 UTC by Fan Jia
Modified: 2020-04-08 21:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1813488 1813489 1821637 (view as bug list)
Environment:
Last Closed: 2020-04-08 21:36:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Fan Jia 2020-03-10 12:34:59 UTC 
Description of problem:
The Upgradeable status of "service-catalog-apiserver" is "Unknown" before enable it.

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-03-09-205007

How reproducible:
always

Steps to Reproduce:
1.Install the cluster
2. check the clusteropeators "service-catalog-apiserver" status
#oc get clusteropeators service-catalog-apiserver -o yaml

Actual results:
1. the Upgradeable status of "service-catalog-apiserver" is "Unknown"
#oc get clusteropeators service-catalog-apiserver -o yaml
status:
  conditions:
  ...
  - lastTransitionTime: "2020-03-10T02:37:48Z"
    reason: NoData
    status: Unknown
    type: Upgradeable

Expected results:
1. The Upgradeable status should be "True" or "False"

Additional info:
If you enable the "service-catalog-apiserver" the Upgradeable status will be "True".
Comment 1 Dan Geoffroy 2020-03-10 13:36:53 UTC 
This does not appear to be a release blocker.  Moving target release to 4.5 and will continue evaluation there.
Comment 2 Jesus M. Rodriguez 2020-04-08 21:30:41 UTC 
This was fixed by another bug.

[jesusr@camaro deploy]$ oc version
Client Version: 4.5.0-0.nightly-2020-04-08-180203
Server Version: 4.4.0-rc.6
Kubernetes Version: v1.17.1
[jesusr@camaro deploy]$ oc get clusteroperators service-catalog-apiserver -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2020-04-08T21:12:10Z"
  generation: 1
  name: service-catalog-apiserver
  resourceVersion: "3780"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/service-catalog-apiserver
  uid: 13302264-c3b8-4460-a4a5-3569bc67cb35
spec: {}
status:
  conditions:
  - lastTransitionTime: "2020-04-08T21:12:12Z"
    reason: AsExpected
    status: "False"
    type: Degraded
  - lastTransitionTime: "2020-04-08T21:12:12Z"
    reason: AsExpected
    status: "False"
    type: Progressing
  - lastTransitionTime: "2020-04-08T21:12:12Z"
    message: 'Available: the apiserver is in the desired state (Removed).'
    reason: AsExpected
    status: "True"
    type: Available
  - lastTransitionTime: "2020-04-08T21:12:12Z"
    message: 'Upgradeable: the apiserver is in a removed state, upgrades are possible.'
    reason: AsExpected
    status: "True"
    type: Upgradeable
  extension: null
  relatedObjects:
  - group: ""
    name: openshift-config
    resource: namespaces
  - group: ""
    name: openshift-config-managed
    resource: namespaces
  - group: ""
    name: openshift-service-catalog-apiserver-operator
    resource: namespaces
  - group: ""
    name: openshift-service-catalog-apiserver
    resource: namespaces
  - group: apiregistration.k8s.io
    name: v1beta1.servicecatalog.k8s.io
    resource: apiservices
  versions:
  - name: operator
    version: 4.4.0-rc.6
Comment 3 Jesus M. Rodriguez 2020-04-08 21:36:03 UTC 
Closing as not a bug for 4.5 since service catalog operators were replaced by jobs.
Note You need to log in before you can comment on or make changes to this bug.