Bug 1358930
Summary: | OSE Deployment Failure during post_install.yml: configure iptables to allow for NFS shares: stderr: iptables: No chain/target/match by that name. | ||
---|---|---|---|
Product: | Red Hat Quickstart Cloud Installer | Reporter: | Landon LaSmith <llasmith> |
Component: | Installation - RHEV | Assignee: | John Matthews <jmatthew> |
Status: | CLOSED ERRATA | QA Contact: | Landon LaSmith <llasmith> |
Severity: | urgent | Docs Contact: | Dan Macpherson <dmacpher> |
Priority: | urgent | ||
Version: | 1.0 | CC: | bthurber |
Target Milestone: | ga | Keywords: | Automation, Triaged |
Target Release: | 1.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-13 16:33:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Landon LaSmith
2016-07-21 19:38:25 UTC
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 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 |