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.
I am reporting this as a bug because this situation is misleading and some customers are trying to use MySQLServerOptions instead of puppet hieradata.
we won't be able to fix properly in THT, probably worth a kcs.