Bug 33097 - fail2ban Upgrade Mageia 8 to 9 screwed up settings
Summary: fail2ban Upgrade Mageia 8 to 9 screwed up settings
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: christian barranco
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-14 12:28 CEST by Per Nelvig
Modified: 2024-06-21 19:08 CEST (History)
0 users

See Also:
Source RPM: fail2ban-1.0.2-1.3.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Per Nelvig 2024-04-14 12:28:39 CEST
Description of problem:

After upgrade to Mageia 9 from 8, the setup for fail2ban were screwed up. 
I found out that the version for Mageia 8 had example setups for different operating system that worked from installation with minimal adjustments. So after copying these from a backup from Mageia 8 it worked again.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Lewis Smith 2024-04-14 20:34:37 CEST
Thank you for the report. It would help if you could give more details about the upgraded config files which did not work, and those you recovered from Mageia 8.

BTAIM Assigning this to squidf who committed v1.0.1 18m ago with the comment "Add Mageia specific configuration files"; also the current version 1.0.2.

Source RPM: fail2ban => fail2ban-1.0.2-1.3.mga9.src.rpm
Assignee: bugsquad => chb0
Severity: enhancement => normal

Comment 2 christian barranco 2024-04-15 21:46:27 CEST
Hi.
Yes, please, provide the list of files you had to adjust.
Just as a reminder, .conf files are system files which can be overwritten. User configuration files have the extension .local
Comment 3 christian barranco 2024-04-27 21:42:41 CEST
Hi. Cannot work on this without more info. Feel free to reopen if still applicable.

Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED

Comment 4 christian barranco 2024-06-21 19:08:47 CEST
no news => closed

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.