Bug 1416927

Summary: [3.4] ansible sometimes gets UNREACHABLE error after iptables restarted
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Wenkai Shi <weshi>
Severity: urgent Docs Contact:
Priority: medium    
Version: 3.4.1CC: aos-bugs, erjones, jialiu, jmatthew, jmeyer, jokerman, knakayam, mmccomas, pdwyer, smunilla, wmeng
Target Milestone: ---   
Target Release: 3.4.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
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 16:37:58 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:
Bug Depends On: 1379189    
Bug Blocks: 1358952, 1416926    

Comment 2 Wenkai Shi 2017-02-06 08:37:31 UTC
Verified with version atomic-openshift-utils-3.4.59-1.git.0.d813eb7, 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] *****************
Monday 06 February 2017  07:15:54 +0000 (0:00:01.452)       0:29:57.164 ******* 
Pausing for 10 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
...

Comment 4 errata-xmlrpc 2017-03-06 16:37:58 UTC
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