Bug 2034638

Summary:	MySQLServerOptions are only defined for standalone MySQL service
Product:	Red Hat OpenStack	Reporter:	Alex Stupnikov <astupnik>
Component:	openstack-tripleo-heat-templates	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED WONTFIX	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	low
Version:	16.2 (Train)	CC:	bdobreli, lmiccini, mburns
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-24 05:28:06 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 Alex Stupnikov 2021-12-21 15:13:46 UTC

Description of problem:

RHOSP overcloud is shipped with Galera cluster. For overcloud nodes OS::TripleO::Services::MySQL composable service points to ../deployment/database/mysql-pacemaker-puppet.yaml. There is no MySQLServerOptions parameter available there, so customers need to use tripleo::profile::base::database::mysql::mysql_server_options hiera parameter to customize MySQL server configuration.

In upstream OS::TripleO::Services::MySQL composable service points to deployment/database/mysql-container-puppet.yaml by default. There is MySQLServerOptions parameter there, so customers can use it to customize MySQL server configuration.

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

Comment 1 Alex Stupnikov 2021-12-21 15:19:29 UTC

I am reporting this as a bug because this situation is misleading and some customers are trying to use MySQLServerOptions instead of puppet hieradata.

Comment 3 Luca Miccini 2023-07-24 05:28:06 UTC

we won't be able to fix properly in THT, probably worth a kcs.