Description of problem: The reference ZTP configuration uses a separate CatalogSource for each operator subscription. These operators will all be in the same disconnected registry in the target use case, and are all contained in the redhat-operators registry in connected environments. Using a single CatalogSource for all operators reduces CPU use by olm indexing and liveness/readiness probes. Version-Release number of selected component (if applicable): 4.10 How reproducible: Always Steps to Reproduce: 1. oc get CatalogSource -A on ZTP installed system Actual results: 5 CatalogSources are reported Expected results: 1 CatalogSource Additional info:
Mark as verified based on results on cnfocto1. policies were combined into config-policy and deployment succeeded with 4.10 ztp-site-generator cnfocto1 ztp-common-cnfocto1.common-cnfocto1-config-policy inform Compliant 4h23m cnfocto1 ztp-common-cnfocto1.common-cnfocto1-du-validator-policy inform Compliant 4h23m cnfocto1 ztp-common-cnfocto1.common-cnfocto1-subscriptions-policy inform Compliant 4h23m cnfocto1 ztp-group-cnfocto1.group-cnfocto1-config-policy inform Compliant 4h23m cnfocto1 ztp-site-cnfocto1.cnfocto1-config-policy inform Compliant 4h23m
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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056