Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1416926 - [3.3] ansible sometimes gets UNREACHABLE error after iptables restarted
[3.3] ansible sometimes gets UNREACHABLE error after iptables restarted
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.3.1
x86_64 Linux
medium Severity urgent
: ---
: 3.3.1
Assigned To: Scott Dodson
Wenkai Shi
:
Depends On: 1379189 1416927
Blocks: qci-ocp
  Show dependency treegraph
 
Reported: 2017-01-26 14:42 EST by Scott Dodson
Modified: 2017-03-06 11:37 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When executing the installer on a remote host that's also included in the inventory the firewall configuration could potentially cause the installer to hang. We have added a 10 second delay after resetting the firewall which should avoid this problem from occurring.
Story Points: ---
Clone Of: 1379189
Environment:
Last Closed: 2017-03-06 11:37:52 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0448 normal SHIPPED_LIVE Important: ansible and openshift-ansible security and bug fix update 2017-03-06 16:36:25 EST

  None (edit)
Comment 2 Wenkai Shi 2017-02-07 02:55:42 EST
Verified with version atomic-openshift-utils-3.3.63-1.git.0.b82a158, the code has effect, installation succeed.

[root@ansible ~]# ansible-playbook -i hosts -v /usr/share/ansible/openshift-ansible/playbooks/byo/config
...
TASK [os_firewall : Wait 10 seconds after disabling firewalld] *****************
Tuesday 07 February 2017  07:24:45 +0000 (0:00:02.106)       0:02:50.519 ****** 
Pausing for 10 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
...
Comment 4 errata-xmlrpc 2017-03-06 11:37:52 EST
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/RHSA-2017:0448

Note You need to log in before you can comment on or make changes to this bug.