Hey, time="2016-04-29T08:04:53.448026514-04:00" level=error msg="Error creating > ImageStreamMapping: imagestreams \"availity-node4\" not found" > go.version=go1.4.2 http.request.host="172.30.147.75:5000" > http.request.id=b0bd9652-f73a-4dd0-8277-d615252d7c8b > http.request.method=PUT http.request.remoteaddr="10.1.1.1:58929" > http.request.uri="/v2/openshift/availity-node4/manifests/latest" > http.request.useragent="docker/1.9.1 go/go1.4.2 > kernel/3.10.0-327.13.1.el7.x86_64 os/linux arch/amd64" > instance.id=0223258b-a32d-444d-ba56-8adcbfe0d05d > vars.name="openshift/availity-node4" vars.reference=latest >
>From the log I see you're getting error upon creating the ImageStreamMapping. The flow is following, upon pushing a new image, docker registry reaches out to master and creates a new ImageStreamMapping (sort of tag information for new image), when accompanying ImageStream does not exist it will create one. Your log specifically shows there's no ImageStream found, for some strange reason. Can you verify if availity-node4 image stream exists in openshift namespace: oc get is -n openshift Can you try to change the name of the image and verify if the problem persists? I'd like to know whether it's a problem with that particular name vs your user access rights, although you've mentioned your userg being admin in openshift namespace. Maciej
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
