Description of problem: The Galera package should definitely Require 'procps-ng' package, otherwise, it won't work. This is reproducible only when not using the '--wsrep-new-cluster' option (So when you want to connect to the cluster with mariadb-server). Version-Release number of selected component (if applicable): All versions and all releases How reproducible: Always Steps to Reproduce: # This needs to be done because it is present in the system (however, users can remove it anytime, so we shouldn't rely on the fact, that it's installed) 1. dnf remove procps-ng -y 2. dnf install galera mariadb-server-galera mariadb 3. Change the config files to the corresponding options 4. systemctl start mariadb Actual results: It won't start and will wait to infinity Expected results: Start the mariadb-server and connect to the cluster. Additional info: When you install the 'procps-ng' package, the 'systemctl start mariadb' process will successfully start the MariaDB server, and everything works as expected This issue should be resolved in all of the products and versions (RHEL-7,8,9; ...) Patch should be simple: Just add 'Requires: procps-ng' to the galera spec file
Also, Honza spotted that upstream has this requirement in their list of packages that should be required by Galera https://github.com/codership/galera/blob/3.x/scripts/mysql/centos/mysql-wsrep.list#L24
PR ready: https://src.fedoraproject.org/rpms/galera/pull-request/8
Merged and built on Rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=79466975
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
FEDORA-2022-5cfe372ab7 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5cfe372ab7
FEDORA-2022-263f7cc483 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-263f7cc483
FEDORA-2022-03350936ee has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-03350936ee
FEDORA-2022-263f7cc483 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-263f7cc483` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-263f7cc483 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-5cfe372ab7 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-5cfe372ab7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5cfe372ab7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-03350936ee has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-03350936ee` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-03350936ee See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-263f7cc483 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-03350936ee has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-5cfe372ab7 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.