[MDEV-5831] Upgrade from MariaDB 5.5.36 via yum fails Created: 2014-03-12  Updated: 2014-03-31  Resolved: 2014-03-26

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.9
Fix Version/s: 5.5.37, 10.0.10

Type: Bug Priority: Major
Reporter: P Ka Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None
Environment:

Centos 6.4, 64-bit



 Description   

Upgrade from MariaDB 5.5.36 via yum fails for MariaDB-server package.

Downloading Packages:
MariaDB-10.0.9-centos6-x86_64-server.rpm                                                                                                            |  51 MB     03:10
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Error in PREIN scriptlet in rpm package MariaDB-server-10.0.9-1.el6.x86_64
 
******************************************************************
A MySQL or MariaDB server package (MariaDB-server-5.5.36-1.el6.x86_64
MariaDB-server-5.5.36-1.el6.x86_64) is installed.
 
The current MariaDB server package is provided by a different
vendor (package MariaDB-server-5.5.36-1.el6.x86_64
MariaDB-server-5.5.36-1.el6.x86_64 is not installed) than Monty Program AB.  Some files may be installed
to different locations, including log files and the service
startup script in /etc/init.d/.
...
This is a brief description of the upgrade process.  Important details
can be found in the MariaDB manual, in the Upgrading section.
******************************************************************
error: %pre(MariaDB-server-10.0.9-1.el6.x86_64) scriptlet failed, exit status 1
error:   install: %pre scriptlet failed (2), skipping MariaDB-server-10.0.9-1.el6
  Verifying  : MariaDB-server-10.0.9-1.el6.x86_64                                                                                                                      1/2
MariaDB-server-5.5.36-1.el6.x86_64 was supposed to be removed but is not!
  Verifying  : MariaDB-server-5.5.36-1.el6.x86_64                                                                                                                      2/2
 
Failed:
  MariaDB-server.x86_64 0:5.5.36-1.el6                                                 MariaDB-server.x86_64 0:10.0.9-1.el6

Other MariaDB related packages upgraded ok (MariaDB-common-10.0.9-1.el6.x86_64, MariaDB-compat-10.0.9-1.el6.x86_64, MariaDB-client-10.0.9-1.el6.x86_64)



 Comments   
Comment by Elena Stepanova [ 2014-03-12 ]

Hi,

While the text that the upgrade offers is weird and should be fixed, in the essence it holds true:

Upgrading directly from MySQL <unrecognized version package MariaDB-server-5.5.36-1.el6.x86_64
MariaDB-server-5.5.36-1.el6.x86_64 is not installed> to MariaDB 10.0 may not
be safe in all cases.  A manual dump and restore using mysqldump is
recommended.  It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.
 
A manual upgrade is required.
 
- Ensure that you have a complete, working backup of your data and my.cnf
  files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages.  Usually this command will
  list the packages you should remove:
  rpm -qa | grep -i '^mysql-'
 
  You may choose to use 'rpm --nodeps -ev <package-name>' to remove
  the package which contains the mysqlclient shared library.  The
  library will be reinstalled by the MariaDB-shared package.
- Install the new MariaDB packages supplied by Monty Program AB
- Ensure that the MariaDB server is started
- Run the 'mysql_upgrade' program

Comment by Elena Stepanova [ 2014-03-12 ]

serg,

Even if we don't support major upgrade via yum, there is still something to fix there. First, the complaint about a different vendor is just weird, since both packages are ours, and something is really wrong with this message:

The current MariaDB server package is provided by a different
vendor (package MariaDB-server-5.5.36-1.el6.x86_64
MariaDB-server-5.5.36-1.el6.x86_64 is not installed) than Monty Program AB.

Secondly, this part doesn't look right either (the cause is probably the same):

Upgrading directly from MySQL <unrecognized version package MariaDB-server-5.5.36-1.el6.x86_64
MariaDB-server-5.5.36-1.el6.x86_64 is not installed> to MariaDB 10.0 may not

Comment by P Ka [ 2014-03-12 ]

Thank you for checking this - Manual upgrade path went smoothly ok.

It would be good to state in the upgrade text that major update via yum is not supported and manual upgrade path needs to applied. Currently that has not been stated in the Release Notes or in Installing MariaDB with yum document page. At least I was having impression that upgrade using yum would be possible (like in minor upgrades).

Comment by Tom Atkinson [ 2014-03-31 ]

These messages are still wrong. Here's what I get updating from 10.0.9 to 10.0.10 on CentOS 6

******************************************************************
A MySQL or MariaDB server package () is installed.

The current MariaDB server package is provided by a different
vendor (package is not installed) than Monty Program AB. Some files may be installed
to different locations, including log files and the service
startup script in /etc/init.d/.

Upgrading directly from MySQL <unrecognized version package is not installed> to MariaDB 10.0 may not
be safe in all cases. A manual dump and restore using mysqldump is
recommended. It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.

A manual upgrade is required.

  • Ensure that you have a complete, working backup of your data and my.cnf
    files
  • Shut down the MySQL server cleanly
  • Remove the existing MySQL packages. Usually this command will
    list the packages you should remove:
    rpm qa | grep -i '^mysql'

You may choose to use 'rpm --nodeps -ev <package-name>' to remove
the package which contains the mysqlclient shared library. The
library will be reinstalled by the MariaDB-shared package.

  • Install the new MariaDB packages supplied by Monty Program AB
  • Ensure that the MariaDB server is started
  • Run the 'mysql_upgrade' program

This is a brief description of the upgrade process. Important details
can be found in the MariaDB manual, in the Upgrading section.
******************************************************************

Comment by Elena Stepanova [ 2014-03-31 ]

Yes, unfortunately it's a new bug, now filed as MDEV-5986.

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