The tag will be created by the build when it runs, but it expects the image stream to exist. When the web console created the build config, it also created the output image stream.
You can recreate it by running: oc create imagestream myapp > On Sep 6, 2017, at 8:59 AM, Tim Dudgeon <tdudgeon...@gmail.com> wrote: > > No. Isn't that what's being created by the build (as its output)? > > Those parameters were taken from the build config that had just successfully > been created and built using the web console, and then the build config > exported as YAML. > > Tim > > > On 06/09/2017 13:44, Cesar Wong wrote: >> Does the myapp image stream exist? >> >>> On Sep 6, 2017, at 6:35 AM, Tim Dudgeon <tdudgeon...@gmail.com> wrote: >>> >>> I'm trying to get to grips with build configs. In this case a Java build >>> using Maven. >>> I managed to get the build to work fine using the web console and now want >>> to allow this to be automated using cli. >>> So I export the build config as YAML using `oc get bc/myapp -o yaml > >>> myapp-bc.yaml`, delete the old one and then try to re-load using the YAML >>> using `oc create -f myapp-bc.yaml` and then start the build. >>> >>> But the build never starts complaining of an 'Invalid output reference'. >>> Presumably this refers to the output section of the YAML that looks like >>> this: >>> >>>> output: >>>> to: >>>> kind: ImageStreamTag >>>> name: myapp:latest >>> Any pointers to what is wrong? >>> >>> Thanks >>> Tim >>> >>> >>> >>> >>> _______________________________________________ >>> users mailing list >>> users@lists.openshift.redhat.com >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users > _______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
