Red Hat Bugzilla – Bug 1380555
[3.3] oc cluster up cannot find default openshift/origin:v3.3.0.32 image
Last modified: 2017-01-26 15:42:19 EST
Description of problem: When running 'oc cluster up' it fails to find the default image: openshift/origin:v3.3.0.32 Version-Release number of selected component (if applicable): 3.3.0.32 How reproducible: Always Steps to Reproduce: 1. Run oc cluster up with no args 2. 3. Actual results: $ 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:v3.3.0.32 image ... Pulling image openshift/origin:v3.3.0.32 FAIL Error: error pulling Docker image openshift/origin:v3.3.0.32 Caused By: Error: Tag v3.3.0.32 not found in repository docker.io/openshift/origin Expected results: A cluster should be provisioned on the users workstation from the orign:v3.3.0.32 image Additional info:
Similar: https://bugzilla.redhat.com/show_bug.cgi?id=1379934
Actually, the default image should be: registry.access.redhat.com/openshift3/ose:v3.3.0.32
We need the default image prefix to be registry.access.redhat.com/openshift3/ose when the binary is an OSE binary (by looking at version info).
My initial thoughts on this are that including code that points to registry.access.redhat.com in the Orgin code base seems clunky. I would much rather include something in the OSE build pipeline that takes care of this. I have reached out to Scott to see if that is an option.
We'd need to patch the OSE code base for this like we've done the image format string. Corey can you open a PR against OSE for this?
Yes, sounds like a good plan to me.
As I understand, I should verify command: oc cluster up --image=registry.access.redhat.com/openshift3/ose and oc cluster up ,which use openshift/origin in mac, is it right?
please verify that "oc cluster up" uses the ose image,
Tested oc(v3.3.1.3) in mac, it works now: [zhangwangs-MacBook-Air:Desktop zhangwang$oc cluster up --image=registry.access.redhat.com/openshift3/ose --create-machine -- Checking OpenShift client ... OK -- Create Docker machine ... Creating docker-machine openshift -- Checking Docker client ... OK -- Checking Docker version ... OK -- Checking for existing OpenShift container ... OK -- Checking for registry.access.redhat.com/openshift3/ose:v3.3.1.3 image ... Pulling image registry.access.redhat.com/openshift3/ose:v3.3.1.3 Pulled 1/4 layers, 25% complete Pulled 2/4 layers, 50% complete Pulled 2/4 layers, 50% complete Pulled 3/4 layers, 75% complete Pulled 4/4 layers, 100% complete Extracting Image pull complete -- Checking Docker daemon configuration ... OK -- Checking for available ports ... OK -- Checking type of volume mount ... Using Docker shared volumes for OpenShift volumes -- Creating host directories ... OK -- Finding server IP ... Using docker-machine IP 192.168.99.101 as the host IP Using 192.168.99.101 as the server IP -- Starting OpenShift container ... Creating initial OpenShift configuration Starting OpenShift using container 'origin' Waiting for API server to start listening OpenShift server started -- Installing registry ... OK -- Installing router ... OK -- Importing image streams ... OK -- Importing templates ... OK -- Login to server ... OK -- Creating initial project "myproject" ... OK -- Server Information ... OpenShift server started. The server is accessible via web console at: https://192.168.99.101:8443 You are logged in as: User: developer Password: developer To login as administrator: oc login -u system:admin
I mis-read the pull request when I closed this. The pull request was for the master branch instead of the enterprise-3.3 branch. Re-Opening and setting back to assigned.
We don't have new puddles now for enterprise-3.3, moved to modified.
The oc cluster now are using the correct registry, but the images is still not released. oc cluster up -- Checking OpenShift client ... OK -- Checking Docker client ... OK -- Checking Docker version ... OK -- Checking for existing OpenShift container ... OK -- Checking for registry.access.redhat.com/openshift3/ose:v3.3.1.8 image ... Pulling image registry.access.redhat.com/openshift3/ose:v3.3.1.8 FAIL Error: error pulling Docker image registry.access.redhat.com/openshift3/ose:v3.3.1.8 Caused By: Error: error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\""
Change to verify, since it works with the pre released image under brew registry。
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0199