Bug 1367199
| Summary: | iptablesSyncPeriod should default to 30s OOTB | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> |
| Component: | Installer | Assignee: | Samuel Munilla <smunilla> |
| Status: | CLOSED ERRATA | QA Contact: | Mike Fiedler <mifiedle> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.0 | CC: | aos-bugs, ghuang, jeder, jokerman, mifiedle, mmccomas, tdawson, tstclair, xtian |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-27 09:44:12 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
Mike Fiedler
2016-08-15 20:22:43 UTC
Default upstream sync period is 30s. The default should be 30s. kubernetes originally had 5s upstream but has since changed it to 30s in the code. Commits pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/735729b08506be08b2a5215a8c1d628cac6d7741 Bug 1367199 - iptablesSyncPeriod should default to 30s OOTB Update the default to thirty seconds. https://github.com/openshift/openshift-ansible/commit/dcfddb882554b7f1a9aa1f4024ba9eb2ebf07204 Merge pull request #2306 from smunilla/BZ1367199 Bug 1367199 - iptablesSyncPeriod should default to 30s OOTB Verified with atomic-openshift-utils-3.3.13-1.git.0.7435ce7.el7.noarch
$ grep "iptables_sync_period" /usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py
iptables_sync_period='30s',
iptablesSyncPeriod is set to 30s by default in node-config.yaml. # grep "iptablesSyncPeriod" /etc/origin/node/node-config.yaml iptablesSyncPeriod: "30s" I will verify, but this is actually hard to verify. The 30 seconds is a MAX limit on the resync. Changes to services or endpoints will still force resyncs at more frequent intervals. tstclair, I think there should be a separate bz/issue opened to establish a MIN sync. Agree? Opened https://bugzilla.redhat.com/show_bug.cgi?id=1371971 to follow up on the min resync interval. Verified in 3.3.0.28 that iptablesResyncPeriod correctly set to 30 seconds during install. 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/RHBA-2016:1933 |