Bug 2226767 - Add Galera components to rhel9/mariadb10-5 image
Summary: Add Galera components to rhel9/mariadb10-5 image
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: mariadb-105-container
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Michal Schorm
QA Contact: rhscl image testing
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-26 12:51 UTC by jakob.englisch
Modified: 2023-08-02 09:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-163541 0 None None None 2023-07-26 12:54:01 UTC

Description jakob.englisch 2023-07-26 12:51:21 UTC
Description of problem:
We're currently building our own variant of rhel9/mariadb-105 due to missing galera components ("dnf install mariadb-server-galera galera"). Galera is disabled by default, hence it shouldn't hurt to add the components. As those components are part of RHEL9 repositories only, we currently maintain a build environment with a working subscription manager just for that - we'd like to get rid of it.

https://catalog.redhat.com/software/containers/rhel9/mariadb-105/61a6084dbfd4a5234d596220?container-tabs=dockerfile - extending line 39 with "mariadb-server-galera galera" would be sufficient.

The installed configuration file /etc/my.cnf.d/galera.cnf disables galera by default using "wsrep_on=0".

Comment 1 Petr Kubat 2023-08-02 09:34:00 UTC
Thanks for the request!

In general every additional package installed into a container above the current set has to go through an approval process. This is due to fact that we would be shipping new packages (galera in this case) for everyone, increasing the image size by a small amount.

If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution.

For information on how to contact the Red Hat production support team, please visit:
    https://access.redhat.com/support


Note You need to log in before you can comment on or make changes to this bug.