Bug 2767

Summary: Use of systemd shows up error for iptables
Product: Mageia Reporter: Dick Gevers <dvgevers>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: dmorganec
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: iptables-1.4.11.1-2.mga2 CVE:
Status comment:
Bug Depends on:    
Bug Blocks: 2120    

Description Dick Gevers 2011-09-18 13:45:53 CEST 
Description of problem:

dmesg shows the line:

systemd[1]: [/etc/rc.d/init.d/iptables:18] Failed to add LSB Provides name firewall.service, ignoring: File exists

Although iptables seems to be running under systemd, I don't like it throwing errors as security is involved.

It so happens that in all files in /etc/rc.d/init.d, iptables (and ip6tables) are the only file which has 2 words on the line "# Provides":

grep Provides iptables
# Provides: iptables firewall

All other init files have only one word on that line!
Comment 1 Dick Gevers 2011-09-18 17:28:44 CEST 
Indeed when I remove the word "firewall" from the "# Provides" line, the warning (error) is not showing up in dmesg anymore !
Dick Gevers 2011-10-07 15:40:16 CEST

Blocks: (none) => 2120

Comment 2 D Morgan 2011-10-22 23:32:43 CEST 
can you test with systemd + initscripts from testing to tell if this is still valid ?

CC: (none) => dmorganec

Comment 3 Dick Gevers 2011-10-23 12:40:31 CEST 
Yes I can, but what is the use if there is no new package iptables and corrected content of /etc/rc.d/init.d/iptables ?
Comment 4 D Morgan 2011-10-24 01:30:32 CEST 
i try to add the .service files asap
Comment 5 D Morgan 2011-10-25 17:29:39 CEST 
Please test new iptables from updates_testing ( it needs systemd from updates_testeing too ).

This new iptables add systemd support.
Comment 6 Dick Gevers 2011-10-25 18:05:58 CEST 
Confirmed okay. Bug can be closed when package is promoted to core.
Comment 7 D Morgan 2011-10-27 18:17:52 CEST 
closing, we are near to push in core

Status: NEW => RESOLVED
Resolution: (none) => FIXED