Question: instalingl the OLM via the CVO

[jianzhangbjz]

I check the payload of the csv, and find many duplicates of YAML file, is it as expected?

[core@ip-10-0-2-239 ~]$ oc adm release extract --from=registry.svc.ci.openshift.org/openshift/origin-release@sha256:6dbef1b08ad892e7c01da342de7fd233d58650e771da151b4fafbef65350b847 --to=release-payload
[core@ip-10-0-2-239 ~]$ ls release-payload/ | grep 30
0000_30_00-namespace.yaml
0000_30_00-namespace_2.yaml
0000_30_01-olm-operator.serviceaccount.yaml
0000_30_01-olm-operator.serviceaccount_2.yaml
0000_30_02-clusterserviceversion.crd.yaml
0000_30_02-clusterserviceversion.crd_2.yaml
0000_30_03-installplan.crd.yaml
0000_30_03-installplan.crd_2.yaml
0000_30_04-subscription.crd.yaml
0000_30_04-subscription.crd_2.yaml
0000_30_05-catalogsource.crd.yaml
0000_30_05-catalogsource.crd_2.yaml
0000_30_06-rh-operators.configmap.yaml
0000_30_06-rh-operators.configmap_2.yaml
0000_30_07-certified-operators.configmap.yaml
0000_30_07-certified-operators.configmap_2.yaml
0000_30_08-certified-operators.catalogsource.yaml
0000_30_08-certified-operators.catalogsource_2.yaml
0000_30_09-rh-operators.catalogsource.yaml
0000_30_09-rh-operators.catalogsource_2.yaml
0000_30_10-olm-operator.deployment.yaml
0000_30_10-olm-operator.deployment_2.yaml
0000_30_11-catalog-operator.deployment.yaml
0000_30_11-catalog-operator.deployment_2.yaml
0000_30_12-aggregated.clusterrole.yaml
0000_30_12-aggregated.clusterrole_2.yaml
0000_30_13-operatorgroup.crd.yaml
0000_30_13-operatorgroup.crd_2.yaml
0000_30_14-olm-operators.configmap.yaml
0000_30_14-olm-operators.configmap_2.yaml
0000_30_15-olm-operators.catalogsource.yaml
0000_30_15-olm-operators.catalogsource_2.yaml
0000_30_16-operatorgroup-default.yaml
0000_30_16-operatorgroup-default_2.yaml
0000_30_17-packageserver.subscription.yaml
0000_30_17-packageserver.subscription_2.yaml

And, they are different, I guess they are from different two manifest files. Why we do that?
For example, the content of 0000_30_16-operatorgroup-default.yaml:

[core@ip-10-0-2-239 ~]$ cat release-payload/0000_30_16-operatorgroup-default.yaml
---
# Source: olm/templates/0000_30_16-operatorgroup-default.yaml
apiVersion: operators.coreos.com/v1alpha2
kind: OperatorGroup
metadata:
  name: global-operators
  namespace: openshift-operators

The content of 0000_30_16-operatorgroup-default_2.yaml:

[core@ip-10-0-2-239 ~]$ cat release-payload/0000_30_16-operatorgroup-default_2.yaml
---
# Source: olm/templates/0000_30_16-operatorgroup-default.yaml
apiVersion: operators.coreos.com/v1alpha2
kind: OperatorGroup
metadata:
  name: global-operators
  namespace: openshift-operators
---
apiVersion: operators.coreos.com/v1alpha2
kind: OperatorGroup
metadata:
  name: olm-operators
  namespace: openshift-operator-lifecycle-manager

@ecordell Could you help clarify this?

[ecordell]

Hi @jianzhangbjz, this is not something we're doing, it looks like a bug in the release pipeline. I will keep this open until we find out how to fix it.

[jianzhangbjz]

Yes, I think so. Thanks for your reply.

[ecordell]

This is fixed now.