Bug 587454

Summary: iptables service runs on reboot, even though the service is disabled
Product: Red Hat Enterprise Linux 5 Reporter: brent Wolfe <bwolfe>
Component: iptablesAssignee: Thomas Woerner <twoerner>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: low    
Version: 5.4CC: cchen
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-07 01:46:10 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:
Bug Depends On:    
Bug Blocks: 1002709    

Description brent Wolfe 2010-04-29 23:17:37 UTC
Description of problem:  iptables service starts at bootup/reboot, even though the service is disabled


Version-Release number of selected component (if applicable):
iptables-1.3.5-5.3.el5_4.1

How reproducible:
100%

Steps to Reproduce:
1.  Reboot/Boot the system.
2. service iptables status

  
Actual results:
Actual result is the iptables service is active on boot or reboot

Expected results:
iptables is not running after reboot/boot

Additional info:

Comment 1 Thomas Woerner 2013-03-22 12:55:45 UTC
Is the service really disabled? Use "chkconfig --list iptables" to verify.

Disabling the service works for me as expected.

Comment 4 Andrius Benokraitis 2013-10-07 01:46:10 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.

Comment 5 Red Hat Bugzilla 2023-09-14 01:21:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days