Bug 1813488 - 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 ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Catalog
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.z
Assignee: Jesus M. Rodriguez
QA Contact: Fan Jia
URL:
Whiteboard:
Depends On: 1813489
Blocks: 1821636
TreeView+ depends on / blocked
 
Reported: 2020-03-14 01:26 UTC by Fan Jia
Modified: 2020-04-30 01:28 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Upgradeable field was not being properly set by the Service Catalog Operators. Consequence: Upgradeable field would appear as Unknown after a fresh cluster install. Fix: The Upgradeable field was properly set by the Service Catalog Operators when they are first run. And subsequently through the various management states. Result:
Clone Of: 1812047
Environment:
Last Closed: 2020-04-30 01:28:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-svcat-apiserver-operator pull 84 0 None closed Bug 1813488: set Upgradeable to true 2020-07-07 13:30:59 UTC
Red Hat Product Errata RHBA-2020:1529 0 None None None 2020-04-30 01:28:29 UTC

Description Fan Jia 2020-03-14 01:26:33 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.3.z

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 2 Fan Jia 2020-04-07 09:33:32 UTC
service-catalog-controller-manager also has the same problem.

Comment 3 Jesus M. Rodriguez 2020-04-08 22:38:46 UTC
As of version 4.3.11, service-catalog-controller-manager-operator shows Upgradeable=True
[jesusr@camaro deploy]$ oc get clusteroperators service-catalog-controller-manager -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2020-04-08T22:17:39Z"
  generation: 1
  name: service-catalog-controller-manager
  resourceVersion: "12051"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/service-catalog-controller-manager
  uid: 5c715d7d-aaee-45cf-89d7-87102c62049d
spec: {}
status:
  conditions:
  - lastTransitionTime: "2020-04-08T22:17:39Z"
    reason: AsExpected
    status: "False"
    type: Degraded
  - lastTransitionTime: "2020-04-08T22:17:39Z"
    message: 'Progressing: the controller manager is in a removed state, therefore
      no changes are being applied.'
    reason: AsExpected
    status: "False"
    type: Progressing
  - lastTransitionTime: "2020-04-08T22:17:39Z"
    message: 'Available: the controller manager is not initially installed, operator
      is available, switch to Managed to enable.'
    reason: AsExpected
    status: "True"
    type: Available
  - lastTransitionTime: "2020-04-08T22:17:39Z"
    reason: AsExpected
    status: "True"
    type: Upgradeable
  extension: null
  relatedObjects:
  - group: operator.openshift.io
    name: cluster
    resource: servicecatalogcontrollermanagers
  - group: ""
    name: openshift-service-catalog-controller-manager-operator
    resource: namespaces
  - group: ""
    name: openshift-service-catalog-controller-manager
    resource: namespaces
  versions:
  - name: operator
    version: 4.3.11

Comment 4 Jesus M. Rodriguez 2020-04-08 22:39:45 UTC
As of 4.3.11 I have confirmed that service-catalog-apiserver-operator shows Unknown. 
[jesusr@camaro deploy]$ oc get clusteroperators service-catalog-apiserver -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2020-04-08T22:16:43Z"
  generation: 1
  name: service-catalog-apiserver
  resourceVersion: "9962"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/service-catalog-apiserver
  uid: aba3a4d7-d5b6-4d8e-bcac-a68c983ff5c4
spec: {}
status:
  conditions:
  - lastTransitionTime: "2020-04-08T22:16:44Z"
    reason: AsExpected
    status: "False"
    type: Degraded
  - lastTransitionTime: "2020-04-08T22:16:44Z"
    reason: AsExpected
    status: "False"
    type: Progressing
  - lastTransitionTime: "2020-04-08T22:16:44Z"
    message: 'Available: the apiserver is in the desired state (Removed).'
    reason: AsExpected
    status: "True"
    type: Available
  - lastTransitionTime: "2020-04-08T22:16:43Z"
    reason: NoData
    status: Unknown
    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.3.11

Comment 8 Fan Jia 2020-04-20 09:01:11 UTC
test result:
cv: 4.3.0-0.nightly-2020-04-18-075046

$ oc get clusteroperators service-catalog-apiserver -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2020-04-20T06:53:49Z"
  generation: 1
  name: service-catalog-apiserver
  resourceVersion: "8381"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/service-catalog-apiserver
  uid: d68e22cc-9416-40eb-9346-e12e49c891db
spec: {}
status:
  conditions:
  - lastTransitionTime: "2020-04-20T06:53:50Z"
    reason: AsExpected
    status: "False"
    type: Degraded
  - lastTransitionTime: "2020-04-20T06:53:50Z"
    reason: AsExpected
    status: "False"
    type: Progressing
  - lastTransitionTime: "2020-04-20T06:53:50Z"
    message: 'Available: the apiserver is in the desired state (Removed).'
    reason: AsExpected
    status: "True"
    type: Available
  - lastTransitionTime: "2020-04-20T06:53:50Z"
    reason: AsExpected
    status: "True"
    type: Upgradeable

2)$ oc get clusteroperators service-catalog-controller-manager -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2020-04-20T06:53:44Z"
  generation: 1
  name: service-catalog-controller-manager
  resourceVersion: "7942"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/service-catalog-controller-manager
  uid: 21666fad-c6d5-4fa2-8c81-ada2a1ed1857
spec: {}
status:
  conditions:
  - lastTransitionTime: "2020-04-20T06:53:44Z"
    reason: AsExpected
    status: "False"
    type: Degraded
  - lastTransitionTime: "2020-04-20T06:53:44Z"
    message: 'Progressing: the controller manager is in a removed state, therefore
      no changes are being applied.'
    reason: AsExpected
    status: "False"
    type: Progressing
  - lastTransitionTime: "2020-04-20T06:53:44Z"
    message: 'Available: the controller manager is not initially installed, operator
      is available, switch to Managed to enable.'
    reason: AsExpected
    status: "True"
    type: Available
  - lastTransitionTime: "2020-04-20T06:53:44Z"
    reason: AsExpected
    status: "True"
    type: Upgradeable

Comment 10 errata-xmlrpc 2020-04-30 01:28:11 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:1529


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