MySQL Bugs: #85954: Invalid config file template for version 5.7 in installer manifest

Bug #85954	Invalid config file template for version 5.7 in installer manifest
Submitted:	14 Apr 2017 21:11	Modified:	21 Oct 2017 6:33
Reporter:	Maxime Therreault	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S2 (Serious)
Version:	1.4	OS:	Windows
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I have a script that execute the installer console to install the community edition of MySQL Server 5.7.11. 

When the product is already installed, the config file still generated (and backuped) using the installer templates coming from the product manifest archive. 

Today, the installer decided to update the product manifest by downloading the new archive (version 422).

The configuration file generated during the installation process is invalid and prevented MySQL to restart after the installation. 

The new template contains new configuration options for INNODB engine that seems unknown to MySQL 5.7. 

Here the error in the server '.err' file at startup: 

... 
2017-04-14T18:27:52.818186Z 0 [ERROR] unknown variable 'innodbclustertypeselection=0.0' 
2017-04-14T18:27:52.818186Z 0 [ERROR] Aborting 
... 

Here what was newly inserted at the end of the 'my.ini' config file: 

... 
# Indicates how is the InnoDB Cluster configured as (Classic, Sandbox, Master or Slave). 
innodbclustertypeselection=0.0 

# Indicates how is the InnoDB Cluster is/will be named. 
innodbclustername=0.0 

# Indicates how many instances will the InnoDB cluster sandbox will have. 
innodbclusterinstances=0.0 

# Holds the InnoDB Cluster Username. 
innodbclusterusername=0.0 

# Indicates the InnoDB Cluster URI. 
innodbclusteruri=0.0 

# Indicates the InnoDB Cluster Port. 
innodbclusterport=0.0 

# Load mysql plugins at start."plugin_x ; plugin_y". 
plugin_load=0.0 

# MySQL server's plugin configuration. 
loose_mysqlx_port=0.0

How to repeat:
Here the command executed:

"C:\Program Files (x86)\MySQL\MySQL Installer for Windows\MySQLinstallerConsole.exe" community install server;5.7.11;x64:*:type=config;port=3312;rootpasswd=XXX;servicename=MYSQL57

I have the same error when I tried a fresh install of server 5.7. I downloaded the windows installation file on 4/14/2017.

Thank you for the bug report. The same error happens if you try to install 5.7.18 instead of 5.7.11?. Thanks.

Doesn't help, we have to stick to version 5.7.11 for now.

Thank you for the feedback. Bugs fix is last released version there isn't backward fix, So the issue happens with version 5.7.18 then it will be processed so if you have an older installer version use it to avoid this issue. Thanks.

This is still happening in with version 5.7.18.
I'm using the following command as a part of a larger script.

MySQLInstallerConsole install -type=Custom -silent "server;5.7.18;x64:*:type=config;servertype=Developer;openfirewall=true;servicename=MySQL;serverid=3307;port=3307;passwd=root;rootpasswd=root;installdir=`"$installdir`";datadir=`"$datadir`""

It has the same problem described by Maxime here. 
I'm also using version 5.7.18 of MySQL Installer Web Community.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

This is still a bug. 

Fresh install of 5.7.19  today. 

Unable to continue.

FYI - I have tried 5.7.19 and 5.7.18, both x86 and x64, with the same issue resulting. 

I have gone back to 5.6.37 x86 and that installs fine and is operating Ok. 

If you require any additional info or testing at my end just let me know.

Hello  Maxime,

Thank you for the bug report.
This reminds me of Bug #87009, could you please confirm if you are affected by Bug #87009 i.e Manifest version is not updating? 
If it is not  the case then may I request you to please provide complete repeatable test case (steps, screenshot etc. - please make it as private if you prefer) to confirm this issue at our end?

Thanks,
Chiranjeevi.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".