Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1445282

Summary: [3.3] Installer fails to add/check iptables rule due to lock on xtables
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Wenkai Shi <weshi>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.1CC: jialiu, jokerman, mmccomas, pdwyer
Target Milestone: ---   
Target Release: 3.3.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously the installer may have failed to add iptables rules if other iptables rules were being updated at the same time. Now the installer waits to obtain a lock when updating iptables rules ensuring that rules are properly created.
Story Points: ---
Clone Of: 1445194 Environment:
Last Closed: 2017-05-17 17:40:29 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: 1445194    
Bug Blocks:    

Comment 3 Wenkai Shi 2017-05-02 06:05:52 UTC
Verified with version openshift-ansible-3.3.73-1.git.0.a4580db.el7.noarch. During installation, run a while loop of iptables command on hosts, installer will be slow down at "TASK [os_firewall : Add iptables allow rules]" step, once stop the while loop, installer continue with normal speed.

[root@master ~]# while true; do iptables -nL; done
...

[root@ansible ~]# ansible-playbook -i hosts -v /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml
...
TASK [os_firewall : Add iptables allow rules] **********************************
...
(slow down here during the "while loop" alive)
...

Comment 5 errata-xmlrpc 2017-05-17 17:40:29 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:1244