[MDEV-19982] Galera-4 package breaks yum update from 10.3 to 10.4 Created: 2019-07-08  Updated: 2021-06-28  Resolved: 2021-06-28

Status: Closed
Project: MariaDB Server
Component/s: Galera, Packaging
Fix Version/s: N/A

Type: Task Priority: Minor
Reporter: Assen Totin (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

In 10.4 the Galera RPM package name has changed from "galera" to "galera-4". This only makes sense if it is supposed to be installed alongside Galera 3, which is partially hinted by the use of a separate subdirectory in /usr/lib64. However, such con-existence is impossible due to overlapping files:

/usr/bin/garb-systemd
/usr/bin/garbd

In the RHEL world, the common and preferred way to update packages (even between significant releases) is via "yum update". While our upgrade guide does say that one need to uninstall 10.3 and then install 10.4, this is more error-prone than simply doing an upgrade, which is, except for this Galera packaging issue, is completely possible.

The issue may be fixed in several ways:

  • If Galera 3 and Galera 4 were indeed meant to co-exist, then rename the two conflicting files in Galera 4. It also a good idea to rename the Galera 4 library as it uses the same library name as Galera 3, and while adding an LD_LIBRARY_PATH to 104. systemd unit file may help, a con-existing 10.3 might still wrongly pick up the Galera 4 library based on how ldd configures its cache.
  • If they were not meant to co-exist, then reusing the name "galera" for the package would had been the best choice; now is a bit too late for this, so add an "Obsoletes: galera" to the RPM spec file instead - as a result, installing the Galera 4 RPM will first remove the Galera 3 RPM.


 Comments   
Comment by Alexey Bychko (Inactive) [ 2021-06-28 ]

rpm upgrade from 10.3 to 10.4 (between all major versions) are not supported.
you need to follow https://mariadb.com/kb/en/upgrading-from-mariadb-103-to-mariadb-104/ and remove 10.3 before installing 10.4

Comment by Elena Stepanova [ 2021-06-28 ]

Major yum upgrade indeed doesn't work for the server on "historical reasons", it is not related to Galera. There was some effort to lift this limitation within MDEV-9584, but the chosen scope was too wide and it never got finished.

However, galera-4 of course should obsolete galera (.3x). It was done long time ago, by commits
https://github.com/MariaDB/galera/commit/7d5a8a35c
and
https://github.com/MariaDB/galera/commit/f58e1a18d

Generated at Thu Feb 08 08:55:50 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.