Description of problem: Imagestream created from image-streams-rhel7.json showing incorrect DOCKER REPO Version-Release number of selected component (if applicable): 3.1.1.6 How reproducible: 100% Steps to Reproduce: #oc create -f /usr/share/openshift/examples/image-streams/image-streams-rhel7.json -n openshift # oc get imagestream -n openshift # oc import-image jenkins -n openshift Actual results: AME DOCKER REPO TAGS UPDATED jenkins 172.30.135.193:5000/openshift/jenkins latest,1 22 minutes ago mongodb 172.30.135.193:5000/openshift/mongodb 2.6,latest,2.4 22 minutes ago mysql 172.30.135.193:5000/openshift/mysql 5.6,latest,5.5 22 minutes ago nodejs 172.30.135.193:5000/openshift/nodejs latest,0.10 22 minutes ago perl 172.30.135.193:5000/openshift/perl 5.20,latest,5.16 22 minutes ago php 172.30.135.193:5000/openshift/php 5.6,latest,5.5 22 minutes ago postgresql 172.30.135.193:5000/openshift/postgresql 9.2,9.4,latest 22 minutes ago python 172.30.135.193:5000/openshift/python 2.7,3.4,latest + 1 more... 22 minutes ago ruby 172.30.135.193:5000/openshift/ruby 2.2,latest,2.0 22 minutes ago Expected results: DOCKER REPO = to registry.access.redhat.com/......... #################### To fix we need to add ImageStream.spec.dockerImageRepository to all imagestream object in /usr/share/openshift/examples/image-streams/image-streams-rhel7.json Example "kind": "ImageStream", "apiVersion": "v1", "metadata": { "name": "jenkins", "creationTimestamp": null }, "spec": { "dockerImageRepository": "registry.access.redhat.com/openshift3/jenkins-1-rhel7:latest", "tags": [ { "name": "latest", "from": { "kind": "ImageStreamTag", "name": "1" } }, { "name": "1", "from": { "kind": "DockerImage", "name": "registry.access.redhat.com/openshift3/jenkins-1-rhel7:latest" } } ] } } ] }
I'm pretty sure this is working as designed, at least once you move to 3.2 (the pulls will actually succeed against the integrated registry). Not sure about 3.1.1.6. Paul/Clayton can provide the most accurate info.
Closing this as a duplicate. *** This bug has been marked as a duplicate of bug 1281735 ***