Description of problem: OSE deployment of RHEV fails during the post_install ansible playbook execution of task [configure iptables to allow for NFS shares] with error: "stderr: iptables: No chain/target/match by that name." ISO Media Version: QCI-1.2-RHEL-7-20160720.t.0 How reproducible: 100% Steps to Reproduce: 1. Install QCI 2. Deploy RHEV+OSE(+CFME) Actual results: Deployment fails at 95% during OSE deployment w/ message "ansible-playbook returned a non-zero exit code during post-installation. Please refer to the log for more information regarding the failure." Deployment log reports "ansible: executing /opt/theforeman/tfm/root/usr/share/gems/gems/fusor_server-1.0.0/lib/modules/ose_installer/playbooks/post_install.yml with /usr/share/foreman/tmp/BQqcpVcYHB/ansible.hosts" ansible.log reports: 2016-07-21 00:28:59,204 p=12096 u=foreman | TASK: [configure iptables to allow for NFS shares] **************************** 2016-07-21 00:28:59,463 p=12096 u=foreman | failed: [jwm1-ose-node1.example.com] => {"changed": true, "cmd": ["iptables", "-I", "OS_FIREWALL_ALLOW", "-p", "tcp", "-m", "state", "--state", "NEW", "-m", "tcp", "--dport", "2049", "-j", "ACCEPT"], "delta": "0:00:00.009415", "end": "2016-07-21 04:28:59.054795", "rc": 1, "start": "2016-07-21 04:28:59.045380", "warnings": []} 2016-07-21 00:28:59,463 p=12096 u=foreman | stderr: iptables: No chain/target/match by that name. Expected results: OSE deployment succeeds
Root cause was answer file format changed for OSE 3.2. Appears to be an unattended consequence causing older format to no longer work. Filed BZ with OCP at BZ 1358951
https://github.com/fusor/fusor/pull/1079
VERIFIED. I was able to deploy OpenShift successfully with no issues during the same task QCI ISO media version: QCI-1.0-RHEL-7-20160809.t.0 2016-08-09 20:02:09,448 p=5633 u=foreman | TASK: [configure iptables to allow for NFS shares] **************************** 2016-08-09 20:02:09,589 p=5633 u=foreman | changed: [cjqyhzwdzu-ose-node1.lab.eng.rdu2.redhat.com] => {"changed": true, "cmd": ["iptables", "-I", "OS_FIREWALL_ALLOW", "-p", "tcp", "-m", "state", "--state", "NEW", "-m", "tcp", "--dport", "2049", "-j", "ACCEPT"], "delta": "0:00:00.004150", "end": "2016-08-10 00:02:10.035745", "rc": 0, "start": "2016-08-10 00:02:10.031595", "stderr": "", "stdout": "", "warnings": []}
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/RHEA-2016:1862