Description of problem:
Version-Release number of selected component (if applicable):
oc cluster up pulling origin images
Steps to Reproduce:
1.oc cluster up
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v184.108.40.206 image ...
Pulling image openshift/origin:v220.127.116.11
Error: error pulling Docker image openshift/origin:v18.104.22.168
Error: manifest unknown: manifest unknown
pulling the images from registry.access.redhat.com
Steve, sending this one your way since you're addressing this. In the 3.4 branch of OSE, the registry for OSE is correct . But I imagine it is reverted in 3.5 because we're starting with origin again? 
Once we pick up the ldflag change  in the OSE rebase we will need to provide the correct envars  during the build and we should be good here. Not sure why we see a regression. I was not under the impression that we had begun the rebases or rewritten any git history in OSE master yet.
Sorry, I forgot to reply to this.
The newer ose rpms (atomic-openshift) are built with these options.
It should be working now I believe on at least atomic-openshift-22.214.171.124 or newer.
Since this bug never reached customers, I am closing it.