Description of problem: When using `oc adm release new`, I'm unable to add a new operator using an override. Version-Release number of selected component (if applicable): $ oc version Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0-201905191700+7bd2e5b-dirty", GitCommit:"7bd2e5b", GitTreeState:"dirty", BuildDate:"2019-05-19T23:52:43Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2019-05-02T11:52:09Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"} How reproducible: Always Steps to Reproduce: 1. oc adm release new --from-release registry.svc.ci.openshift.org/origin/release:4.2 --to-dir release-image cluster-etcd-operator=quay.io/hexfusion/cluster-etcd-operator:latest 2. fd 0000_12 release-image Actual results: No manifests from the etcd operator are present in the directory. Expected results: $ fd 0000_12 release-image release-image/0000_12_etcd-operator_00_namespace.yaml release-image/0000_12_etcd-operator_01_cluster-member-request-crd.yaml release-image/0000_12_etcd-operator_01_config.crd.yaml release-image/0000_12_etcd-operator_01_operator.cr.yaml release-image/0000_12_etcd-operator_02_service.yaml release-image/0000_12_etcd-operator_03_configmap.yaml release-image/0000_12_etcd-operator_04_clusterrolebinding.yaml release-image/0000_12_etcd-operator_05_serviceaccount.yaml release-image/0000_12_etcd-operator_06_deployment.yaml release-image/0000_12_etcd-operator_07_clusteroperator.yaml Additional info: Patch is here: https://github.com/openshift/oc/pull/2
The override is not used to find the operators that need to be included in the release-image, but only to override the already included operators. The --from-* are responsible for choosing the operators that need to end up in release image. using the overrides to also affect what operators end up should probably be an RFE. https://jira.coreos.com/secure/RapidBoard.jspa?rapidView=165&view=detail
So what is the process today? Is there a doc I missed?
From slack: > crawford: What do you think about https://github.com/openshift/origin/issues/21061? Is this a bug that needs to be fixed or is it my understanding of how release images should be built. > Clayton Coleman: itβs definitely bug, should have been fixed I'm gonna reopen this.
Version: # ./oc version Client Version: openshift-clients-4.3.0-201910250623-48-g8c30708e Kubernetes Version: v1.11.0+d4cacc0 Steps: 1. docker login 2. # ./oc adm release new --from-release registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2019-11-12-000306 --to-dir release-image cluster-etcd-operator=quay.io/hexfusion/cluster-etcd-operator:latest ... info: Loading override quay.io/hexfusion/cluster-etcd-operator:latest cluster-etcd-operator ... # ls release-image/ |grep "0000_12" 0000_12_etcd-operator_00_namespace.yaml 0000_12_etcd-operator_00_staticpod-rolebinding.yaml 0000_12_etcd-operator_00_staticsync-rolebinding.yaml 0000_12_etcd-operator_01_config.crd.yaml 0000_12_etcd-operator_01_operator.cr.yaml 0000_12_etcd-operator_02_service.yaml 0000_12_etcd-operator_03_configmap.yaml 0000_12_etcd-operator_03_secret.yaml 0000_12_etcd-operator_04_clusterrolebinding.yaml 0000_12_etcd-operator_05_serviceaccount.yaml 0000_12_etcd-operator_06_deployment.yaml 0000_12_etcd-operator_06_static_pod_demonset.yaml 0000_12_etcd-operator_06_static_sync_demonset.yaml 0000_12_etcd-operator_07_clusteroperator.yaml
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, 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/RHBA-2020:0062