Bug 1282986

Summary: fail2ban-firewalld action files firewallcmd-mulitport, firewallcmd-allports have iptables-blocktype dependency
Product: [Fedora] Fedora EPEL Reporter: shadowym
Component: fail2banAssignee: Orion Poplawski <orion>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: epel7CC: athmanem, bctpe4hbiu, orion, vonsch
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Unspecified   
URL: https://github.com/fail2ban/fail2ban/issues/1254
Whiteboard:
Fixed In Version: 0.9.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-22 05:58:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description shadowym 2015-11-18 00:11:11 UTC 
Description of problem:
firewallcmd-multiport.conf and firewallcmd-allports.conf have a:

before = iptables-blocktype.conf

statement.  However there is no iptables-blocktype.conf file include in any of the fail2ban RPM's.  This statement should be changed to iptables-common.conf which already has the necessary blocktype statement. Alternatively an iptables-blocktype.conf file should be included.

I am using this one.
https://github.com/breauxaj/puppet-fail2ban/blob/master/files/original/rhel/action.d/iptables-blocktype.conf
Comment 1 shadowym 2015-11-18 00:14:44 UTC 
I am running the latest stable version from EPEL v7 as of right now.  So v0.9.3-1
Comment 2 Mike McCune 2016-03-28 23:15:27 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 3 Orion Poplawski 2019-11-22 05:58:12 UTC 
This should have been fixed in 0.9.5.