Update catasb to deploy openshift 3.7 images

notes.md

You can now deploy Ansible Service Broker on OpenShift 3.7 using catasb.

Important notes

• If you want to deploy the broker on OpenShift 3.7 you must add the following to config/my_vars.yml:

  origin_image_tag: latest
  openshift_client_version: '3.7'
  

• The '3.7' client is not compatible with OpenShift 3.6 (at least with respect to the service-catalog). This means that if you change only the image tag or only the client version you will get a failure that looks something like (in this case I omitted the openshift_client_version):

  TASK [openshift_setup : Run oc cluster up to start the cluster] *********************************************
  fatal: [localhost]: FAILED! => {
  "changed": true, 
  "cmd": "/home/dzager/bin/oc cluster down && 
  /home/dzager/bin/oc cluster up --routing-suffix=172.17.0.1.nip.io --public-hostname=172.17.0.1 
  --host-pv-dir=/persistedvolumes --image=docker.io/openshift/origin 
  --version=latest  --service-catalog=true",
  "delta": "0:10:20.654250", "end": "2017-08-31 10:18:23.772059", 
  "failed": true, "rc": 1, "start": "2017-08-31 10:08:03.117809", 
  "stderr": "", "stderr_lines": [], "stdout": 
  "Starting OpenShift using docker.io/openshift/origin:latest ...
  -- Checking OpenShift client ... OK
  -- Checking Docker client ... OK
  -- Checking Docker version ... OK
  -- Checking for existing OpenShift container ... OK
  -- Checking for docker.io/openshift/origin:latest image ... OK
  -- Checking Docker daemon configuration ... OK
  ...
  -- Installing service catalog ... FAIL
  Error: failed to start the service catalog apiserver: timed out waiting for the condition",
  ...

• The bind operation doesn't work in OpenShift 3.7, but you probably already knew that.

Let me know if I missed anything.

Hope this helps, Zager