You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect the issue is not tied up to a single command but I run into it when I tried to create a new release from an existing image.
running the following command (notice incorrect —from-release flag)
oc adm release new —from-release=registry.svc.ci.openshift.org/origin/release:4.2 cluster-kube-apiserver-operator=quay.io/polynomial/origin-cluster-kube-apiserver-operator:latest --to-image=quay.io/polynomial/origin-release:latest
gives me the following output
info: Loading override quay.io/polynomial/origin-cluster-kube-apiserver-operator:latest
cluster-kube-apiserver-operator
info: Included 1 images from 1 input operators into the release
error: unable to create a release: operator "cluster-kube-apiserver-operator" contained an
invalid image-references file: no input image tag named "hypershift"
running (notice incorrect -from-release flag)
oc adm release new -from-release=registry.svc.ci.openshift.org/origin/release:4.2 cluster-kube-apiserver-operator=quay.io/polynomial/origin-cluster-kube-apiserver-operator:latest --to-image=quay.io/polynomial/origin-release:latest
is better but not perfect
error: open rom-release=registry.svc.ci.openshift.org/origin/release:4.2: no such file or
directory
however the following command
oc adm release new --key=val --from-release=registry.svc.ci.openshift.org/origin/release:4.2 cluster-kube-apiserver-operator=quay.io/polynomial/origin-cluster-kube-apiserver-operator:latest --to-image=quay.io/polynomial/origin-release:latest
reports an unknow flag
Error: unknown flag: --key
Usage:
oc adm release new [SRC=DST ...] [flags]
Examples:
# Create a release from the latest origin images and push to a DockerHub repo
oc adm release new --from-image-stream=4.1 -n origin --to-image
docker.io/mycompany/myrepo:latest
....
I would expect that cases 1 and 2 would behave the same way as 3.
The text was updated successfully, but these errors were encountered:
I suspect the issue is not tied up to a single command but I run into it when I tried to create a new release from an existing image.
running the following command (notice incorrect
—from-release
flag)gives me the following output
running (notice incorrect
-from-release
flag)is better but not perfect
however the following command
reports an unknow flag
I would expect that cases
1
and2
would behave the same way as3
.The text was updated successfully, but these errors were encountered: