Bug 1835886

Summary: VPA won't install due to "CRD version not served"
Product: OpenShift Container Platform Reporter: Joel Smith <joelsmith>
Component: NodeAssignee: Joel Smith <joelsmith>
Status: CLOSED ERRATA QA Contact: Weinan Liu <weinliu>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: aos-bugs, jokerman, weinliu
Target Milestone: ---   
Target Release: 4.5.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: 2020-07-13 17:39:04 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 Joel Smith 2020-05-14 16:56:07 UTC
Description of problem:

The VPA's CSV references CRD versions that are not served (v1beta1) which results in a failure to install due to an updated check in OLM.

The CSV status stays stuck in "Pending" as a result and the VPA operator never gets installed.

How reproducible:

100%

Steps to Reproduce:
The CSV with v1beta1 CRDs is getting this in the CSV status:

$ oc get clusterserviceversion.operators.coreos.com/verticalpodautoscaler.v4.5.0 -n openshift-vertical-pod-autoscaler -o yaml

Actual results:

... snip ...

  requirementStatus:
  - group: apiextensions.k8s.io
    kind: CustomResourceDefinition
    message: CRD version not served
    name: verticalpodautoscalercheckpoints.autoscaling.k8s.io
    status: NotPresent
    version: v1
  - group: apiextensions.k8s.io
    kind: CustomResourceDefinition
    message: CRD version not served
    name: verticalpodautoscalers.autoscaling.k8s.io
    status: NotPresent
    version: v1

Expected results:

  requirementStatus:
  - group: apiextensions.k8s.io
    kind: CustomResourceDefinition
    message: CRD is present and Established condition is true
    name: verticalpodautoscalercheckpoints.autoscaling.k8s.io
    status: Present
    uuid: 93094f41-f1c6-42f8-bdd3-e3122636f92e
    version: v1
  - group: apiextensions.k8s.io
    kind: CustomResourceDefinition
    message: CRD is present and Established condition is true
    name: verticalpodautoscalers.autoscaling.k8s.io
    status: Present
    uuid: a3878321-183a-47c0-8e67-d66a5b691eca
    version: v1

Comment 4 Weinan Liu 2020-05-20 09:08:13 UTC
Verified to get fixed on 


$ oc version
Client Version: 4.4.0-rc.10
Server Version: 4.5.0-0.nightly-2020-05-19-041951
Kubernetes Version: v1.18.2


[weinliu@vm251-93 ~]$ oc get clusterserviceversion.operators.coreos.com/verticalpodautoscaler.v4.5.0 -n openshift-vertical-pod-autoscaler -o yaml|grep -i Present -B5

...snip...
      version: v1
    group: ""
    kind: ServiceAccount
    message: ""
    name: vertical-pod-autoscaler-operator
    status: Present
...snip...

Comment 5 errata-xmlrpc 2020-07-13 17:39:04 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:2409