Bug 2019805

Summary:	Galera doesn't work without 'procps-ng' package
Product:	[Fedora] Fedora	Reporter:	Lukas Javorsky <ljavorsk>
Component:	galera	Assignee:	Michal Schorm <mschorm>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	36	CC:	damien.ciabrini, fdinitto, hhorak, ljavorsk, mbayer, mschorm
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	galera-26.4.11-1.fc36 galera-26.4.11-1.fc35	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2024974 2024979 (view as bug list)		Environment:
Last Closed:	2022-05-07 04:34:50 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:
Bug Depends On:
Bug Blocks:	2024974, 2024979, 2042526

Description Lukas Javorsky 2021-11-03 11:19:39 UTC

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

Comment 1 Lukas Javorsky 2021-11-03 11:45:01 UTC

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

Comment 2 Lukas Javorsky 2021-11-24 09:39:16 UTC

PR ready: https://src.fedoraproject.org/rpms/galera/pull-request/8

Comment 3 Lukas Javorsky 2021-12-01 09:56:41 UTC

Merged and built on Rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=79466975

Comment 4 Ben Cotton 2022-02-08 21:09:48 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 5 Fedora Update System 2022-04-28 15:54:43 UTC

FEDORA-2022-5cfe372ab7 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5cfe372ab7

Comment 6 Fedora Update System 2022-04-28 15:55:30 UTC

FEDORA-2022-263f7cc483 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-263f7cc483

Comment 7 Fedora Update System 2022-04-28 15:56:14 UTC

FEDORA-2022-03350936ee has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-03350936ee

Comment 8 Fedora Update System 2022-04-29 05:47:57 UTC

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.

Comment 9 Fedora Update System 2022-04-29 07:41:35 UTC

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.

Comment 10 Fedora Update System 2022-04-29 08:08:18 UTC

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.

Comment 11 Fedora Update System 2022-05-07 04:34:50 UTC

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.

Comment 12 Fedora Update System 2022-05-08 01:46:47 UTC

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.

Comment 13 Fedora Update System 2022-05-08 02:02:08 UTC

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.