RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
/etc/security/user_map.conf getting overwritten with mariadb-server upgrade

Version-Release number of selected component (if applicable):
The file seem start come with the following version
mariadb-server-3:10.3.27-3.module+el8.3.0+8972+5e3224e9
and issue with 
mariadb-server-3:10.3.28-1.module+el8.3.0+10472+7adc332a

How reproducible:
Yes, try make change to the file /etc/security/user_map.conf and yum update mariadb

Steps to Reproduce:
1. Install mariadb-server-3:10.3.27-3.module+el8.3.0+8972+5e3224e9
2. make change to the file /etc/security/user_map.conf
3. update mariadb-server-3:10.3.28-1.module+el8.3.0+10472+7adc332a

Actual results:
The file has been overwrited.

Expected results:
The file should not overwrite.

Additional info:
It seem that upstream aware of the issue and fixed in 10.3.23 & 10.4.13. 
https://jira.mariadb.org/browse/MDEV-21886
This file must be labelled "config noreplace" in the RPM spec file which will prevent RPM from touching the file if the currently existing one has any alterations.

*** Bug 1989853 has been marked as a duplicate of this bug. ***