Operator-Catalog-Initialization-Failed

Issue

A partner has submitted the metadata but failing the first test for catalog-initialization. Usually, A partner will fail this test if there is a duplicate CSV in their metadata.zip file, or having a duplicate operator (one which manages/owns the same CRD as another already certified operator) with a different package name.

Environment

• Operator Config section for Operator Project in Red Hat Partner Connect web site

Resolution

Method 1: Delete existing operator

Delete existing operator and submit using the same metadata bundle. The backend engineering team needs to be involved in the process and a ticket will need to be opened.

This will cause the operator to be removed from the catalog and will break the upgrade cycle for any customer currently using the existing operator.

Method 2: Recreate your operator

Recreate your operator and its metadata to own/manage a differently named CRD and with a different packagename. This will allow the existing operator to continue to be used by customers and will put your new operator into the embedded OperatorHub.