Bug 1996213 - Bump Cluster Resource Override Admission Operator to use v1 APIs
Summary: Bump Cluster Resource Override Admission Operator to use v1 APIs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.z
Assignee: Joel Smith
QA Contact: MinLi
URL:
Whiteboard:
Depends On:
Blocks: 2014667
TreeView+ depends on / blocked
 
Reported: 2021-08-20 20:58 UTC by Ryan Phillips
Modified: 2021-10-27 16:15 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2014667 (view as bug list)
Environment:
Last Closed: 2021-10-26 17:22:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-resource-override-admission-operator pull 66 0 None None None 2021-08-27 22:16:40 UTC
Red Hat Product Errata RHBA-2021:3935 0 None None None 2021-10-26 17:22:48 UTC

Description Ryan Phillips 2021-08-20 20:58:53 UTC
Description of problem:
Bump Cluster Resource Override Admission Operator to use v1 APIs

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Sunil Choudhary 2021-09-05 17:51:50 UTC
Checked on 4.9.0-0.nightly-2021-09-05-040736, Cluster Resource Override operator is failing to deploy with below error. @Joel, could you help check?

api-server resource not found installing CustomResourceDefinition clusterresourceoverrides.operator.autoscaling.openshift.io: GroupVersionKind apiextensions.k8s.io/v1beta1, Kind=CustomResourceDefinition not found on the cluster. This API may have been deprecated and removed, see https://kubernetes.io/docs/reference/using-api/deprecation-guide/ for more information.

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2021-09-05-040736   True        False         4h26m   Cluster version is 4.9.0-0.nightly-2021-09-05-040736

Comment 9 MinLi 2021-09-10 09:50:11 UTC
Hi, Joel

with the 4.9 release Candidate nightly 4.9.0-0.nightly-2021-09-06-055314, I install from operatorhub, but reproduce the issue in  Comment 5.
From https://coreos.slack.com/archives/CB95J6R4N/p1631026334146200, I think the Candidate nightly have the operator builds in the staging index image.

Comment 11 MinLi 2021-09-14 11:11:23 UTC
@Joel

Comment 12 MinLi 2021-09-14 11:16:39 UTC
@Joel
Thanks for your instructions in detail, I can install the operator successfully! 
It's awesome!

Comment 18 errata-xmlrpc 2021-10-26 17:22:37 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 (OpenShift Container Platform 4.9.4 bug fix update), 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-2021:3935


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