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

Bug 1455656

Summary:	[3.5] iptables spams the logs with the rules every time iptables-restore is called
Product:	OpenShift Container Platform	Reporter:	Ben Bennett <bbennett>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Status:	CLOSED ERRATA	QA Contact:	Meng Bo <bmeng>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	aos-bugs, bmeng, jeder, smunilla, yadu
Target Milestone:	---
Target Release:	3.5.z
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: We logged the iptables rules at too low of a log level. Consequence: The logs fill with iptables noise. Fix: Change the level at which they are logged. Result: Much more useful logs.	Story Points:	---
Clone Of:	1455655	Environment:
Last Closed:	2017-08-10 05:25:32 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:	1455655
Bug Blocks:

Description Ben Bennett 2017-05-25 17:21:51 UTC

+++ This bug was initially created as a clone of Bug #1455655 +++

Description of problem:
At log level 3 OpenShift dumps the complete iptables rules to the log.

Version-Release number of selected component (if applicable):
3.5.0

How reproducible:
Every time log level is set to 3 or higher.

Steps to Reproduce:
1. Set the log level to 3
2. Start openshift
3. Watch the logs

Actual results:

Masses of iptables rules printed to the log.

Expected results:

No rules printed at reasonable log levels.

Comment 1 Ben Bennett 2017-05-31 13:44:23 UTC

PR https://github.com/openshift/ose/pull/765

Comment 5 Yan Du 2017-06-02 05:53:59 UTC

Test on OCP 3.5
openshift v3.5.5.21
kubernetes v1.5.2+43a9be4

No iptable rules printed in log when setting log level to 3 and rules printed to the log when log level is 5.

@Ben Could you please move bug to ON_QA, then QE could verify it.

Comment 7 errata-xmlrpc 2017-08-10 05:25:32 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/RHEA-2017:1716