| Bug #69006 | CentOS 6: Upgrading MySQL-client 5.6.11 from 5.5.23 rpm fails | ||
|---|---|---|---|
| Submitted: | 19 Apr 2013 6:59 | Modified: | 26 Apr 2013 13:53 |
| Reporter: | Simon Mudd (OCA) | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
| Version: | 5.6.11 | OS: | Linux (CentOS 6 x86_64) |
| Assigned to: | Balasubramanian Kandasamy | CPU Architecture: | Any |
[19 Apr 2013 6:59]
Simon Mudd
[19 Apr 2013 7:19]
Simon Mudd
Work around is to do the following: [root@myserver ~]# rpm -e MySQL-client [root@myserver ~]# rpm -ivh MySQL-client-5.6.11-1.el6.x86_64.rpm Preparing... ########################################### [100%] 1:MySQL-client ########################################### [100%] [root@myserver ~]# However, it should not be necessary to do this.
[22 Apr 2013 17:58]
MySQL Verification Team
Thank you for the bug report. Verified as described: [root@centos64 Downloads]# yum localinstall MySQL-client-5.6.11-1.el6.x86_64.rpm Loaded plugins: fastestmirror, refresh-packagekit, security Setting up Local Package Process Examining MySQL-client-5.6.11-1.el6.x86_64.rpm: MySQL-client-5.6.11-1.el6.x86_64 Cannot install package MySQL-client-5.6.11-1.el6.x86_64. It is obsoleted by installed package MySQL-client-5.5.23-1.el6.x86_64 Nothing to do [root@centos64 Downloads]# uname -a Linux centos64.br 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed Mar 13 00:26:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@centos64 Downloads]#
[22 Apr 2013 18:02]
MySQL Verification Team
Forgot to paste: [root@centos64 Downloads]# rpm -e MySQL-client [root@centos64 Downloads]# rpm -ivh MySQL-client-5.6.11-1.el6.x86_64.rpm Preparing... ########################################### [100%] 1:MySQL-client ########################################### [100%] [root@centos64 Downloads]#
[24 Apr 2013 12:20]
Balasubramanian Kandasamy
For upgrades, it is necessary to clean up any earlier MySQL installations. In effect, the update is performed by removing the old installations and installing the new one. Detailed steps can be found at below documentation. http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-11.html Thanks, Bala
[24 Apr 2013 17:40]
Simon Mudd
I'm sorry but I don't agree. This behaviour has changed compared to 5.6.10 which was GA. Also note: (a) the MySQL-server rpm does not seem to behave the same which is why the reported problem is only for the MySQL-client rpm. That is not consistent. (b) as far as I know this problem only happens on CentOS 6, not CentOS 5. Again not consistent. Note: if we want to upgrade we deliberately do this. That is: 1. stop MySQL 2. run yum to install to the new "higher" version. 3. Do the "upgrade tasks required to upgrade to 5.6.X 4. start MySQL normally I understand that you may not expect the upgrade to happen completely automatically, though I don't see that as being totally impossible, but the way you prevent this by generating an error saying the MySQL 5.6.11 is "obsolete" appears just broken and wrong. I think this changed behaviour also means that if you are not careful and _do_ have 5.6.11 client rpm installed and yum upgrade MySQL-client you'll get a downgrade back to 5.5 which makes no sense either, thus forcing us to setup 2 different repos for each major MySQL version. That should not be necessary, and also behaves differently to behaviour of upgrades of MySQL rpms from: 5.0 to 5.1, 5.1 to 5.5, at least as far as I remember. So if you really want to prevent these upgrades from 5.5 to 5.6, provide an rpm %preinst hook to avoid that (to prevent the newer rpm being installed) but also provide a mechanism to enable us to override that (something on the filesystem so we can say: "yes, upgrade, I know what I'm doing".)
[26 Apr 2013 12:33]
Ramesh Maddali
To explain in detail about the fix we made; we have fixed RPM spec file towards few known issues about Obsoletes, so its just this time to clean the corrupt spec file, we need to 'remove and install' and subsequently for future releases rpm -Uvh or yum localinstall will work. For example: I tried with 5.5.31 and 5.6.11 and the upgrade went through without any issues. [root@myserver tmp]# rpm -qa |grep MySQL MySQL-server-5.6.11-1.el6.x86_64 perl-DBD-MySQL-4.013-3.el6.x86_64 [root@myserver tmp]# rpm -ivh MySQL-client-5.5.31-1.el6.x86_64.rpm Preparing... ########################################### [100%] 1:MySQL-client ########################################### [100%] [root@myserver tmp]# rpm -qa |grep MySQL MySQL-server-5.6.11-1.el6.x86_64 perl-DBD-MySQL-4.013-3.el6.x86_64 MySQL-client-5.5.31-1.el6.x86_64 [root@myserver tmp]# rpm -Uvh MySQL-client-5.6.11-1.el6.x86_64.rpm Preparing... ########################################### [100%] 1:MySQL-client ########################################### [100%] HTH -ramesh
[26 Apr 2013 13:53]
Simon Mudd
So you are saying the issue is with the 'broken' MySQL 5.5.23 rpms we are using ? (broken from a packaging point of view). If that's the case then ok, as for me at least upgrading all 5.5 servers to .31 would be too time-consuming when I'm looking anyway at moving to 5.6 and would prefer to spend the time getting 5.6 up and running.
[15 May 2013 10:02]
Balasubramanian Kandasamy
Hi Simon, Yes, we have fixed the issue in 5.5.31 rpms and requested customer to perform a clean installation of 5.6.11 (removing existing installation) so that any later upgrades will be smooth. Thanks for understanding. - Bala
