Bug 790123

Summary:	F17-Branched Can't start ip6tables.service
Product:	[Fedora] Fedora	Reporter:	Frank Murphy <frankly3d>
Component:	iptables	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	psabata, twoerner
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-09 11:14:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Frank Murphy 2012-02-13 17:43:01 UTC

Description of problem: Can't start ip6tables.service 

~]# systemctl status ip6tables.service
ip6tables.service - IPv6 firewall with ip6tables
	  Loaded: loaded (/usr/lib/systemd/system/ip6tables.service; enabled)
	  Active: failed (Result: exit-code) since Mon, 13 Feb 2012 17:33:34 +0000; 8s ago
	 Process: 2615 ExecStart=/usr/libexec/ip6tables.init start (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/ip6tables.service

Feb 13 17:33:34 testvm ip6tables.init[2615]: ip6tables: Applying firewall rules: libkmod: index_mm_open: open(/lib/modules/3.3.0-0.r... denied
Feb 13 17:33:34 testvm ip6tables.init[2615]: libkmod: kmod_search_moddep: could not open moddep file '/lib/modules/3.3.0-0.rc3.git3....ep.bin'
Feb 13 17:33:34 testvm ip6tables.init[2615]: ip6tables-restore v1.4.12.2: ip6tables-restore: unable to initialize table 'filter'



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


How reproducible: Always since up to F17


Steps to Reproduce:
1.  systemctl enable ip6tables.service
2.
3.
  
Actual results: not start


Expected results: ip6 start


Additional info:

Comment 1 Fedora End Of Life 2013-04-03 17:54:33 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Thomas Woerner 2014-01-09 11:14:43 UTC

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.