Operator-Packagename-Uniqueness Failed

Issue

A partner has submitted the metadata but failing with packagename uniquess test. If a partner is submitted the metadata for the first time the scan will bind the ospid of their project to that packagename. If they try to submit a follow up bundle with a different packagename to the same project the scan will fail. The scan compares all packagenames of certified and community operators against the metadata bundle. If there are any duplicates the scan will fail.

Environment

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

Resolution

Method 1: Verify the packagename used the first time scanned

If this is not the first time you are running the operator config test verify that the packagename did not change from the original submitted files. The packagename can be found in the package.yaml file submitted:

Example package.yaml

channels:
- currentCSV: wordpress-operator.v0.0.1
  name: alpha
defaultChannel: alpha
packageName: wordpress-operator-certified

Method 2: Add CERTIFIED to the name

If the partner has a community operator with the same packagename this test will fail. We recommend adding "-certified" to the name of the package to avoid this conflict.

Method 3: More Information

If the workaround in Method 1 or 2 is not an acceptable solution, a partner needs to open a support ticket and provide the following information:

• The Project URL

• Package Name

• Bundle Archive