Bug 1696260

Summary:	[RFE]: Add definitions for MariaDB Galera
Product:	Red Hat Enterprise Linux 8	Reporter:	Michal Schorm <mschorm>
Component:	firewalld	Assignee:	Eric Garver <egarver>
Status:	CLOSED ERRATA	QA Contact:	Štěpán Němec <snemec>
Severity:	low	Docs Contact:
Priority:	low
Version:	8.0	CC:	egarver, hhorak, rkhan, todoleza
Target Milestone:	rc	Keywords:	FutureFeature, Triaged, Upstream
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	firewalld-0.8.2-6.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-18 14:58:48 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 Michal Schorm 2019-04-04 12:40:20 UTC

Hello,
this is tracking bug for adding firewall definitions for MySQL & MariaDB replication services.

The default port for MySQL & MariaDB database is 3306 - which is well known and already set in firewalld.

On the top of that, MariaDB Galera replication (for making database clusters) utilizes aditional ports.
This piece of documentation covers them:
http://galeracluster.com/documentation-webpages/firewalld.html

However since we already have "mysql" definition, I'd suggest to create the new one named "galera" or "mariadb-galera".
I'd split them like this beacuse I wouldn´t like to have replication ports opened when not using replication.

Comment 1 Eric Garver 2019-07-01 20:25:35 UTC

The RHEL-8 package is "galera" so we should call the service "galera" as well.



[root@rhel8 030]# dnf search galera
...
galera.x86_64 : Synchronous multi-master wsrep provider (replication engine)
...
mariadb-server-galera.x86_64 : The configuration files and scripts for galera replication

Comment 12 Štěpán Němec 2021-02-03 14:16:02 UTC

https://galeracluster.com/library/documentation/firewall-settings.html states that Galera Cluster multicast replication uses both UDP and TCP on port 4567, but the commit included in the above pull request only configures TCP.
(See also https://github.com/firewalld/firewalld/pull/724#discussion_r533666044 for related developer discussion.)

Is TCP-only OK?

Comment 22 errata-xmlrpc 2021-05-18 14:58:48 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 (firewalld bug fix and enhancement update), 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-2021:1643