Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

local installation failed due to a new OC binary version #270

Open
irosenzw opened this issue Oct 16, 2018 · 1 comment
Open

local installation failed due to a new OC binary version #270

irosenzw opened this issue Oct 16, 2018 · 1 comment

Comments

@irosenzw
Copy link

Running the script on a centos 7.5 VM and getting the following error:

TASK [openshift_setup : debug] ************************************************************************************************************************************************************************************
ok: [localhost] => {
"msg": "Looking at oc cluster up command: '/root/bin/oc cluster up --routing-suffix=192.168.100.90.nip.io --public-hostname=192.168.100.90 --base-dir=/tmp/openshift.local.clusterup --tag=v3.11 --image=docker.io/openshift/origin-\${component}:\${version} --enable=service-catalog,router,registry,web-console,persistent-volumes,sample-templates,rhel-imagestreams,automation-service-broker,template-service-broker'"
}

TASK [openshift_setup : Run oc cluster up to start the cluster] ***************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": "/root/bin/oc cluster down && /root/bin/oc cluster up --routing-suffix=192.168.100.90.nip.io --public-hostname=192.168.100.90 --base-dir=/tmp/openshift.local.clusterup --tag=v3.11 --image=docker.io/openshift/origin-\${component}:\${version} --enable=service-catalog,router,registry,web-console,persistent-volumes,sample-templates,rhel-imagestreams,automation-service-broker,template-service-broker", "delta": "0:00:00.215353", "end": "2018-10-16 02:41:17.937460", "msg": "non-zero return code", "rc": 1, "start": "2018-10-16 02:41:17.722107", "stderr": "Error: unknown flag: --routing-suffix\n\n\nUsage:\n oc cluster up [flags]\n\nExamples:\n # Start OpenShift using a specific public host name\n oc cluster up --public-hostname=my.address.example.com\n\nOptions:\n --base-dir='': Directory on Docker host for cluster up configuration\n --image='openshift/origin-${component}:${version}': Specify the images to use for OpenShift\n --public-hostname='': Public hostname for OpenShift cluster\n --server-loglevel=0: Log level for OpenShift server\n\nUse "oc options" for a list of global command-line options (applies to all commands).", "stderr_lines": ["Error: unknown flag: --routing-suffix", "", "", "Usage:", " oc cluster up [flags]", "", "Examples:", " # Start OpenShift using a specific public host name", " oc cluster up --public-hostname=my.address.example.com", "", "Options:", " --base-dir='': Directory on Docker host for cluster up configuration", " --image='openshift/origin-${component}:${version}': Specify the images to use for OpenShift", " --public-hostname='': Public hostname for OpenShift cluster", " --server-loglevel=0: Log level for OpenShift server", "", "Use "oc options" for a list of global command-line options (applies to all commands)."], "stdout": "", "stdout_lines": []}
to retry, use: --limit @/root/catasb/ansible/setup_local_environment.retry

PLAY RECAP ********************************************************************************************************************************************************************************************************
localhost : ok=43 changed=12 unreachable=0 failed=1

You can see that the OC binary uploaded to https://apb-oc.s3.amazonaws.com/ was changed today (16.10.2018) and the OC version was changed from 3.11-alpha to 4.0-alpha.

[root@localhost ~]# oc version
oc v4.0.0-alpha.0+6f594bd-337
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

@jmontleon
Copy link
Contributor

jmontleon commented Oct 16, 2018

set origin_image_tag: v3.11 or whatever version you want in your my_vars.yml. We're working on getting latest working, which has moved onto v4.0, but the installation options have changed significantly and it might be awhile before it works correctly.

You'll want to re pull fusor/catasb master as well. There have been a couple recent changes that may be helpful to pulling the correct client version, especially for v3.11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants