Hide Forgot
Description of problem: When creating heat stack which selects IP failover mode for OpenShift router, ansible-playbook would failed at task "Deploy Openshift IP failover for router". This looks like to be caused by a existing bug in OCP 3.3: https://bugzilla.redhat.com/show_bug.cgi?id=1332432 Version-Release number of selected component (if applicable): openshift-on-openstack v0.9.1 # oc version oc v3.3.0.34 kubernetes v1.3.0+52492b4 openshift v3.3.0.34 kubernetes v1.3.0+52492b4 How reproducible: 100% Steps to Reproduce: 1.Create a heat stack which is OCP3.3 + IP failover mode for router 2. 3. Actual results: Heat stack was failed. Check the ansible log on bastion host: TASK [Deploy Openshift IP failover for router] ********************************* task path: /var/lib/ansible/playbooks/ipfailover.yml:13 Using module file /usr/lib/python2.7/site-packages/ansible/modules/core/commands/command.py <ghuang6-neutron-lb-openshift-master-0.example.com> ESTABLISH SSH CONNECTION FOR USER: cloud-user <ghuang6-neutron-lb-openshift-master-0.example.com> SSH: EXEC ssh -vvv -o ControlMaster=auto -o ControlPersist=600s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=cloud-user -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/%h-%r ghuang6-neutron-lb-openshift-master-0.example.com '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-cbaufsurovkgobuxxsndnuxwaydehrez; /usr/bin/python'"'"'"'"'"'"'"'"' && sleep 0'"'"'' fatal: [ghuang6-neutron-lb-openshift-master-0.example.com]: FAILED! => { "changed": true, "cmd": [ "oadm", "ipfailover", "--create", "--service-account=ipfailover", "--interface=eth0", "--selector=region=infra", "--replicas=2", "--virtual-ips=192.168.0.4", "--credentials=/etc/origin/master/openshift-router.kubeconfig" ], "delta": "0:00:00.237775", "end": "2016-10-10 02:20:02.918713", "failed": true, "invocation": { "module_args": { "_raw_params": "oadm ipfailover --create --service-account=ipfailover --interface=eth0 --selector='region=infra' --replicas=2 --virtual-ips=\"192.168.0.4\" --credentials=/etc/origin/master/openshift-router.kubeconfig", "_uses_shell": false, "chdir": null, "creates": null, "executable": null, "removes": null, "warn": true }, "module_name": "command" }, "rc": 1, "start": "2016-10-10 02:20:02.680938", "stderr": "Flag --credentials has been deprecated, use --service-account to specify the service account the ipfailover pod will use to make API calls\n error: serviceaccounts \"ipfailover\" already exists", "stdout": "--> Creating IP failover ipfailover ...\n deploymentconfig \"ipfailover\" created\n--> Failed", "stdout_lines": [ "--> Creating IP failover ipfailover ...", " deploymentconfig \"ipfailover\" created", "--> Failed" ], "warnings": [] } to retry, use: --limit @/var/lib/ansible/playbooks/main.retry Expected results: Stack created successfully. Additional info:
Should be fixed by https://github.com/redhat-openstack/openshift-on-openstack/pull/266
This is caused by OCP3.3 bug https://bugzilla.redhat.com/show_bug.cgi?id=1332432 A workaround for openshift-on-openstack is merged now: https://github.com/redhat-openstack/openshift-on-openstack/commit/2cc2e9fb8e176fff96b6075df2635a31ff2f4684
fixed in 0.9.2
Verified with openshift-on-openstack v0.9.2 + OSP8 + OCP3.3 openshift v3.3.0.35 kubernetes v1.3.0+52492b4 etcd 2.3.0+git IPfailover works well although the command returns "Failed". "rc": 1, "start": "2016-10-13 01:58:07.250624", "stderr": "Flag --credentials has been deprecated, use --service-account to specify the service account the ipfailover pod will use to make API calls\n error: serviceaccounts \"ipfailover\" already exists", "stdout": "--> Creating IP failover ipfailover ...\n deploymentconfig \"ipfailover\" created\n--> Failed", "stdout_lines": [ "--> Creating IP failover ipfailover ...", " deploymentconfig \"ipfailover\" created", "--> Failed" ], "warnings": [] } ...ignoring Current workaround works, we need remove the workaround once BZ#1332432 is fixed. So move it to verified currently.