Bug #87957 MySQL Installer Does Nothing if Upgrading from 5.6.37 to 5.7.19
Submitted: 3 Oct 2017 20:57 Modified: 4 Oct 2017 14:40
Reporter: Jay Jaeger Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.6.37 OS:Windows (X64)
Assigned to: CPU Architecture:Any

[3 Oct 2017 20:57] Jay Jaeger
Description:
On one day I upgraded from 5.6.10 to 5.6.37 using the downloaded install package mysql-installer-community-5.6.37.0.msi, which worked as expected.

However, the next day when I want to upgrade to 5.7.19 using the downloaded install package mysql-installer-community-5.7.19.0.msi, it did not offer any upgrades for MySQL Server.  In fact, at first, it offered no upgrades at all.

After doing a Catalog...Update operation, and waiting a day (after posting an initial question on this issue on the forum), the product catalog did show two instances of MySQL Server 5.7.19 dated 7/17/2017 (as well as other older versions of MySQL Server and other "products").  After doing that, I did see little yellow upgrade icons for Connector/ODBC (currently at version 5.3.8) and Connector/J (currently at version 5.1.42), but nothing for Server, Workbench, Documentation or Samples and Examples.

After posting on the community forum, I waited for a day and seeing no help forthcoming, I proceeded to "Add...".  That dialog had an entry to add 5.7.19, but nothing for upgrading.  I then proceeded down that path.

(This install worked, but did some very unfriendly things that I will report as their own bugs.)

This "silently" REMOVED version 5.6.37, removed the Windows service MYSQL56.

I then tried to remove version 5.7.19, to see if that would restore my old version.  Nope.  I would have either had to restore from a backup, or proceed to configure 5.7.19, which I was able to do.

But it did not offer ANY upgrade assistance, did not remember where my defaults file had been, created a new data directory.  In short, it did not do an upgrade at all, it did a new install.

(Once I reconfigured 5.7.19, I was able to do a mysql_upgrade, but this did not go the way I expected or wanted it to).

How to repeat:
I have not actually tried to repeat the issue, but if it is repeatable, this is how I did things.

1.  Install 5.6.10, X64, using MSI mysql-installer-community-5.6.10.1.msi
2.  NOTE:  Install to a different path, say D:\Pro\MySQL
3.  Create your own data directory, and configure MySQL to use that.
4.  Upgrade to 5.6.37 using mysql-installer-community-5.6.37.0.msi
5.  Try to upgrade to 5.7.19 using mysql-installer-community-5.7.19.0.msi
[3 Oct 2017 21:23] Jay Jaeger
NOTE:  Add a step in configuring 5.6 after the initial install:

3.5:  Relocate my.ini file to a different location

I had:

D:\db\mysql - location of my.ini (specified when starting the service)
D:\db\mysql\data - data directory
[4 Oct 2017 7:32] Chiranjeevi Battula
Hello Jay,

Thank you for the bug report.
This is most likely duplicate of Bug #79315, please see Bug #79315
More information:
https://forums.mysql.com/read.php?11,653989,654037#msg-654037

Thanks,
Chiranjeevi.
[4 Oct 2017 14:40] Jay Jaeger
Yes, I agree that #79315 describes the same situation as this report.  I didn't spot it because I searched for the words "installer".