tripleo

MySQLServerOptions are only defined for standalone MySQL service

Bug #1955490 reported by Alexey Stupnikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
High
Unassigned

Bug Description

If overcloud is configured to use Galera cluster, then 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.

If overcloud is configured to use standalone MySQL server, then for overcloud nodes OS::TripleO::Services::MySQL composable service points to deployment/database/mysql-container-puppet.yaml. There is MySQLServerOptions parameter there, so users can use it to customize MySQL server configuration.

Downsream BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2034638

Bogdan Dobrelya (bogdando)
Changed in tripleo:
status: New → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.