This BZ is to track inclusion of openshift-ansible installer issue filed here in OCP3.4. https://github.com/openshift/openshift-ansible/issues/2635 It's a simple fix that would allow use of flannel as the backend SDN for OCP. Until it's fixed, users must stay on an older version of flannel.
Commit pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/0a0f0fc3126179b01f45f76cc85bc30cee428070 Update flannel etcd vars for 0.5.5 flannel-0.5.5 uses different variable names in /etc/sysconfig/flannel. This writes both the old and next variable name to the file for quick compatibility. Fixes #2635 Fixes Bug 1391515
Verified with openshift-ansible-3.4.18-1.git.0.ed7dac0.el7.noarch + RHEL7.3 + docker1.12 + flannel-0.5.5-1.el7.x86_64 flaneld service was running well on all nodes. $ cat /etc/sysconfig/flanneld |grep -v "#" FLANNEL_ETCD_ENDPOINTS=https://flannel-73-1-openshift-master-0.example.com:2379 FLANNEL_ETCD_PREFIX=/openshift.com/network FLANNEL_OPTIONS=--iface eth1 --etcd-cafile=/etc/origin/node/flannel.etcd-ca.crt --etcd-keyfile=/etc/origin/node/flannel.etcd-client.key --etcd-certfile=/etc/origin/node/flannel.etcd-client.crt S2I build succeed, and route can be accessed.
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:0066