Bug 1973194

Summary:	rpminspect failure - badfuncs test (issues with 'resolveip' binary)
Product:	Red Hat Enterprise Linux 9	Reporter:	Michal Schorm <mschorm>
Component:	mariadb	Assignee:	Zuzana Miklankova <zmiklank>
Status:	CLOSED ERRATA	QA Contact:	Jakub Heger <jheger>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	databases-maint, hhorak, ljavorsk, zmiklank
Target Milestone:	beta	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	mariadb-10.5.13-1.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 12:42:41 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:

Comment 4 Honza Horak 2021-11-19 13:17:09 UTC

These functions have made problems for ages, but we've never taken this much seriously. The reason is that resolveip binary is only used in scripts and their branches that are usually not used in RHEL environment -- we call the mysql_install_db script with --rpm option, while the resolveip is only called when --rpm is not used [2].

Therefore I believe we should create a rule for rpminspect to not report the problematic functions in this binary.

[1] https://gitlab.com/redhat/centos-stream/rpms/mariadb/-/blob/c9s/mariadb-prepare-db-dir.sh#L100
[2] https://github.com/MariaDB/server/blob/5566cbadb03856aba9c236b131f544490cd2bee4/scripts/mysql_install_db.sh#L425-L441

Comment 8 Michal Schorm 2021-12-17 09:19:33 UTC

https://gitlab.com/redhat/centos-stream/rpms/mariadb/-/commit/793527ec8541bccae84ab8f47a8a08388c78d64e

Comment 15 errata-xmlrpc 2022-05-17 12:42:41 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: mariadb), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2381