+++ This bug was initially created as a clone of Bug #1725977 +++

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