Description of problem: When running the installer on one of the systems they are trying to install in the cluster, it hangs when it reaches the Start and enable iptables task. The customer eventually cancels it (ctrl+c) and restarts the installer (where it then immediately succeeds). Version-Release number of selected component (if applicable): # rpm -qa | grep -ie ansible -ie ose -ie openshift tuned-profiles-atomic-openshift-node-3.2.1.17-1.git.0.6d01b60.el7.x86_64 atomic-openshift-master-3.2.1.17-1.git.0.6d01b60.el7.x86_64 openshift-ansible-lookup-plugins-3.2.33-1.git.0.899bad8.el7.noarch atomic-openshift-utils-3.2.33-1.git.0.899bad8.el7.noarch atomic-openshift-3.2.1.17-1.git.0.6d01b60.el7.x86_64 atomic-openshift-node-3.2.1.17-1.git.0.6d01b60.el7.x86_64 atomic-openshift-sdn-ovs-3.2.1.17-1.git.0.6d01b60.el7.x86_64 ansible-2.2.0-0.5.prerelease.el7.noarch openshift-ansible-3.2.33-1.git.0.899bad8.el7.noarch openshift-ansible-filter-plugins-3.2.33-1.git.0.899bad8.el7.noarch openshift-ansible-playbooks-3.2.33-1.git.0.899bad8.el7.noarch atomic-openshift-clients-3.2.1.17-1.git.0.6d01b60.el7.x86_64 openshift-ansible-docs-3.2.33-1.git.0.899bad8.el7.noarch openshift-ansible-roles-3.2.33-1.git.0.899bad8.el7.noarch Seems at least related to: https://bugzilla.redhat.com/show_bug.cgi?id=1379189 (don't think it is exactly the same issue though. Per Scott Dodson's suggestion, customer tried adding "ansible_connection=local" to the host running the ansible installer. This did not work. Customer is unable to try running the installer from an external system at this time.