Bug 57590

Summary: iptables update configures service off at all runlevels, affecting next boot
Product: [Retired] Red Hat Linux Reporter: Christopher Johnson <ckjohnson>
Component: iptablesAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-17 13:21:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christopher Johnson 2001-12-17 03:27:00 UTC 
Description of Problem:
Updating iptables with the iptables-1.2.4-0.71.2.i386.rpm configures
iptables service off at all runlevels.

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

How Reproducible:
100%

Steps to Reproduce:
1.chkconfig --list iptables [shows on at runlevels 345]
2.rpm -Fvh iptables-1.2.4-0.71.2.i386.rpm 
3.chkconfig --list iptables [shows off at all runlevels] 

Actual Results:
The iptables rules in effect remain in effect until the next boot, when
iptables quietly ceases to protect the system.

This causes a significant security exposure to be quietly introduced into
systems relying on iptables.

Expected Results:
Updating iptables should leave the iptables service configured on at all
runlevels which it was previously on.

Additional Information:
I have not tested the iptables updates for other RH versions 6.x or 7.2 but
someone should.