Bug 675512

Summary: cannot start iptables at boot: no iptables.service file
Product: [Fedora] Fedora Reporter: Matt Kinni <matt>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-08 12:22:35 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 Matt Kinni 2011-02-06 05:16:41 UTC
Description of problem:
Hi, there is no iptables.service file, so it's impossible to get the iptables service started at boot.

Version-Release number of selected component (if applicable):
I tried both F14 and rawhide versions of initscripts and systemd, no packages seam to provide iptables.service

How reproducible:
always

Steps to Reproduce:
1. systemctl enable iptables.service
2. doesn't work
3.
  
Actual results:
doesn't work

Expected results:
works

Additional info:

Comment 1 Michal Schmidt 2011-02-07 12:20:19 UTC
> I tried both F14 and rawhide versions of initscripts and systemd

Did you test this on a full Rawhide system, or merely an F14 with these two packages taken from Rawhide?


On my Rawhide system:

# systemctl enable iptables.service
iptables.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig iptables on

What output do you get instead?
Do you have the file /etc/rc.d/init.d/iptables ?

Comment 2 Lennart Poettering 2011-02-08 12:22:35 UTC
iptables is still a SysV service, and thus has no native systemd service file. systemd supports SysV services just fine. So I don't really see a bug here? 

Closing, feel free to reopen if I am misunderstanding the situation here.