Description of problem:

When installing an SNO through ZTP, the performance profile does not apply. I think this is may be due the source-crs in the cnf-features-deploy repo adding an additional catalogsource for the performance-addon-operator. This causes the operator to appear in two catalogs:

NAME                                               CATALOG                                AGE
performance-addon-operator                         Red Hat Operators                      20h
performance-addon-operator                         Openshift Performance Addon Operator   6h29m

That seems to prevent the operator from being installed properly (at least in my case). The solution seems to be to update the subscription [1] to use redhat-operators as the source. Also, the extra catalogsource [2] is not required.

[1] https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.9/ztp/source-crs/PaoSubscription.yaml
[2] https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.9/ztp/source-crs/PaoSubscriptionCatalogSource.yaml

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

How reproducible:

Not sure - happened the first time I tried to install 4.9.

Steps to Reproduce:

1. Attempt to deploy an SNO using ZTP (gitops workflow with ArgoCD and RHACM)
2. Create a performance profile for the SNO.

Actual results:

The performance profile was not applied. The policy showed as NonCompliant with this message:
NonCompliant; violation - couldn't find mapping resource with kind PerformanceProfile, please check if you have CRD deployed

Expected results:

The performance profile is applied.

Additional info:

None