Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1679453

Summary: Cannot remove clusterserviceclass
Product: OpenShift Container Platform Reporter: Min Woo Park <mpark>
Component: Service BrokerAssignee: Shawn Hurley <shurley>
Status: CLOSED ERRATA QA Contact: Zhang Cheng <chezhang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, chuo, shurley
Target Milestone: ---   
Target Release: 3.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-11 05:38:34 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:

Comment 3 Shawn Hurley 2019-02-25 14:25:45 UTC 
If you want to remove all the APB's you could delete the ClusterServiceBroker that tells the service catalog to talk to the broker.

To update this field you could remove the white_list:

~~~~~
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: v1
data:
  broker-config: "registry:\n  - type: rhcc\n    name: rh\n    url:  https://registry.redhat.io\n
    \   org:  \n    tag:  v3.11\n white_list: []\n\n    black_list: [.*automation-broker-apb$]\n\n
    ...
~~~~~


OR you could change the black_list:
broker-config: "registry:\n  - type: rhcc\n    name: rh\n    url:  https://registry.redhat.io\n
    \   org:  \n    tag:  v3.11\n white_list: []\n\n    black_list: [.*-apb$]\n\n
Comment 4 Zhang Cheng 2019-02-27 06:42:27 UTC 
Changing status to VERIFIED since LGTM and no issue follow user guide.
Comment 6 errata-xmlrpc 2019-04-11 05:38:34 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-2019:0636