Bug 1838872

Summary: ROKS: CVO not honoring exclude annotation for ClusterOperator resources
Product: OpenShift Container Platform Reporter: Cesar Wong <cewong>
Component: Cluster Version OperatorAssignee: Cesar Wong <cewong>
Status: CLOSED ERRATA QA Contact: liujia <jiajliu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, jokerman, wking
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: IBMROKS
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1841239 (view as bug list) Environment:
Last Closed: 2020-07-13 17:41:00 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:
Bug Depends On:    
Bug Blocks: 1841239    

Description Cesar Wong 2020-05-22 00:09:06 UTC
Description of problem:
For the IBM ROKS use case, we rely on annotations in operator manifests to let the CVO know whether that manifest should be excluded. In 4.5.x releases, the CVO is ignoring that annotation for cluster operators and creating them anyway.

Version: 4.5 nightly

How reproducible:
Always

Steps to Reproduce:
1. Create a hosted control plane cluster with a 4.5 nightly release

Actual results:
Cluster operator resources that should be excluded such as machine-api-operator are getting created inside the cluster.

Expected results:
Cluster operator resources with the exclude annotation are not created on target cluster.

Comment 4 liujia 2020-05-29 02:00:50 UTC
@cewong
Due to this is a ROKS bug and it's "ON_QA" status now, could u give a verify from IBM ROKS side and comment here? Then I can continue the regression test work from ocp side. Thx!

Comment 5 Cesar Wong 2020-05-29 16:05:26 UTC
Verified on 4.5.0-0.nightly-2020-05-29-105132

Comment 6 liujia 2020-06-02 06:11:42 UTC
Verified installation on 4.5.0-0.nightly-2020-05-30-025738.
Verified upgrade from v4.4.6 to 4.5.0-0.nightly-2020-06-01-165039.

Comment 7 errata-xmlrpc 2020-07-13 17:41:00 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