Bug 2050954

Summary:	mariadb-connector-odbc/Sanity/mariadb-simple fails on (Access denied for user 'root'@'localhost')
Product:	Red Hat Enterprise Linux 8	Reporter:	Lukas Javorsky <ljavorsk>
Component:	mariadb-connector-odbc	Assignee:	Michal Schorm <mschorm>
Status:	CLOSED WONTFIX	QA Contact:	RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	databases-maint, ljavorsk, mmuzila
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-05 07:28:19 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 Lukas Javorsky 2022-02-05 09:03:48 UTC

Description of problem:
This issue has been found during the Gating tests on mariadb-10.5.13-1 version.
https://dashboard.osci.redhat.com/#/artifact/redhat-module/aid/14125?focus=id:846c7c7dc478-1

It is manually reproducible as well.

My intuition is that this could be caused by mariadb-server which is using the unix-socket authentication as a default, while mariadb-connector-odbc does not if it's not defined in the configuration file (https://mariadb.com/kb/en/about-mariadb-connector-odbc/#general-connection-parameters).

This test can be fixed by creating GRANT on root user as well, which has been done for RHEL-9 tests (https://src.osci.redhat.com/tests/mariadb-connector-odbc/c/a2a5a9c29433143d83f65f33dddaba4d7fd7f25c?branch=master).

These are just my assumptions, they are not 100%, so it will need more investigation.


How reproducible:
Always

Steps to Reproduce:
1. Run the /CoreOS/mariadb-connector-odbc/Sanity/mariadb-simple test
2.
3.

Actual results:
[ISQL]ERROR: Could not SQLConnect
[28000][unixODBC][ma-3.1.12]Access denied for user 'root'@'localhost'

Expected results:
Passes

Comment 2 RHEL Program Management 2023-08-05 07:28:19 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.