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

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 222981

Summary:	"service iptables stop" fails because ip_conntrack cannot be unloaded.
Product:	Red Hat Enterprise Linux 5	Reporter:	Thomas Woerner <twoerner>
Component:	iptables	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED NOTABUG	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0	CC:	bhinson, davem, dmalcolm, dzickus, kajtzu, konradr, rbiba, rlerch, tao
Target Milestone:	---	Keywords:	Regression, Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-01-17 16:25:18 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:	212839
Bug Blocks:

Comment 2 RHEL Program Management 2007-01-17 11:01:10 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 RHEL Program Management 2007-01-17 11:06:07 UTC

This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

Comment 4 Thomas Woerner 2007-01-17 11:54:46 UTC

Fixing this bug in iptables is a regression.

Comment 5 Thomas Woerner 2007-01-17 16:25:18 UTC

The real problem was a misconfiguration in an old lokkit version, which used
netfilter IPv4 modules for the IPv6 firewall, which is not a good idea at all.

Closing "NOT A BUG"