MySQL Bugs: #69878: More foolish installer issues .. SIGH

Bug #69878	More foolish installer issues .. SIGH
Submitted:	31 Jul 2013 10:57	Modified:	20 Jul 2015 23:04
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S3 (Non-critical)
Version:	5.6.13	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
I have downloaded mysql-installer-community-5.6.13.0.msi.

After running for a while attached dialog appears .. (to be continued)

How to repeat:
(to be continued)

Suggested fix:
FIRE SOMEBODY.  This has lasted for 5 years now!

the dialog

Attachment: installer.jpg (image/jpeg, text), 43.26 KiB.

And here is what is wrong:

1) 
I already have MySQL 5.0.96, 5.1.70 and 5.5.32 installed (+ a few MariaDB instances).  There is nothing to upgrade for MySQL 5.1 or 5.5 servers.

Connecting to the instances shows this: 

SELECT VERSION()
/*
version()  
-----------
5.1.70-community     
*/

SELECT VERSION()
/*
version()  
-----------
5.5.32     
*/

2)
So I don't want any upgrade to run against 5.1 or 5.5 (obviously).  I also don't want WB 5.2 replaced by 6.0 (I actually have both of them installed, but don't use the 'integrated installer' to manage those). 

I check the option 'skip the check for upgrade ...". Now it just GOES IN CIRCLES FOREVER, returns to the same dialog and I cannot proceed.  After some iterations it is even no longer possible to activate this checkbox anymore (it becomes 'greyed out').

.. and

.. both 5.1.70 and 5.5.32 were installed with .msi installers as upgrades on top of previous versions in the same tree (5.1.70 with the 'standalone' installer (the opnly option for this version) and 5.5.32 with the 5.5.32 'integrated installer'.

Besides I don't intend to reply to questions here! I had enough.

Please DO SOME TESTING BEFORE RELEASING! And don't bother the World with such nonsense. There has been issues with almsot each and every .msi installer released for the last many years.

PERIOD!

Peter,

To make you happy, I can confirm that I've got the same dialog box here, suggesting to upgrade to 5.5.32 while I clearly have it installed, via one of older MySQL Installers:

C:\Program Files\MySQL\MySQL Server 5.5\bin>mysql -uroot -proot -P3312 test
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 16
Server version: 5.5.32 MySQL Community Server (GPL)

Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
...

So, at least some part of the problem is real. On the other hand, isn't it minor (comparing even to your older numerous more serious Installer related bug reports)?

Thanks Valeriy .. you are a charm!

I have cooled down a little bit.  But there is hardly a .msi isntaller rom oracle that does not cause problems on specific configurations and there were few over the last 5 years that did not. And it is wasting time.

Nobody can convince me that this installer was ever tested properly.

I suggest that the 'integrated installer' should not attempt to upgrade other major server versions. Ther are multiple installation methods (including 'mysqld -install' command.  In this case the registry has no records of a server except in HKCM\..\services. And multiple instances of the same major version may exist with the 'mysqld -install' command).  Also there is no guarantee than an instance is running. I cannot see how it is safe to detect what is actually installed.

You can offer *optionally* to upgrade connectors, the notifier, WB etc. But make it possible to deselect this as well as to skip upgrade check and don't go in circles.

It is not minor.  Not quite at least.  Because I cannot upgrade to 5.6.13 with htis installer without doing something that I don't want to do. If I attempt teh installer 'goes in circles'.

Well, I just unchecked everything but 5.6 related line before proceeding and happily updated 5.6.12 to 5.6.13 on 64-bit Windows 7.

FYI, I am not in Oracle for 11 months already. Let's celebrate :)

I know you are not in Oracle now! Didn't I call you 'a charm'! Would I do that with an Oracle person? :-)

Anyway .. let me try the installer again to see if the 'going in circles' is repeatable.

It did not go in circles this time.  I check "skip .." and uncheck the other server versions as well as WB. Not able to determine if I did something slightly different in the interface last time.

So now you say i was not "a charm" while in Oracle? Oh, well... 7+ years wasted? :)

Thank you for the bug report.

Explantion follows

Attachment: again_nonsense.jpg (image/jpeg, text), 17.12 KiB.

explanation: It happened again when upgradeing from 5.6.13 to 5.6.14 using mysql-installer-community-5.6.14.0.msi this showed up!

But before that I HAD JUST upgraded 5.5.33 successfully to 5.3.34 using  mysql-5.5.34-winx64.msi

Do anybody here (else than Miguel) read bug reports about the installers?

Maybe we can soon have a clear answer: Can the 'integrated installers' and 'standalone installers' be used randomly?

Besides the 5.6.14 integrated installer destroyed my 5.7.1 isntallation in an attempt to upgrade it to 5.7.2 (and further mysql-installer-community-5.7.2.0-m12.msi cannot configure the service so that it will start - not even after uninstalling 5.7 and also after uninstalling the installer itself.  

BTW: an installer that installs itself before installing what it is supposed to install? complete nonsense - at least as long as it does not work, what it never really did - at least not with more MySQL servers on same machine.).

Further it wnated to upgrade WB from 6.0.2 to 6.07.  It allowed it. it downloaded (but it took ages) but did not upgrade Workbench! After showing "downloading .. 100%' nothing more happened.

Posted by developer:
 
This bug was reported against an old version of the MySQL Installer.
MySQL Installer 1.4.x does not show these incorrect behaviors anymore.