Bug #74622 | Passive mode install does not work | ||
---|---|---|---|
Submitted: | 29 Oct 2014 16:56 | Modified: | 10 Nov 2015 17:34 |
Reporter: | George Thornton | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S2 (Serious) |
Version: | 5.6.21.1 | OS: | Windows |
Assigned to: | Jose Gabriel Valencia Ornelas | CPU Architecture: | Any |
[29 Oct 2014 16:56]
George Thornton
[29 Oct 2014 20:51]
MySQL Verification Team
Thank you for the bug report.
[9 Sep 2015 0:42]
Jose Gabriel Valencia Ornelas
It was tested against other older installer from 1.3.X and Installer 1.4.X with /passive works in the same way need more information about the functionality requested or additional information
[9 Oct 2015 1:00]
Bugs System
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".
[9 Oct 2015 1:44]
George Thornton
The passive install doesn't work. Currently using the /passive parameter results in the full GUI experience, but passive installs are not meant to do that. They are meant to be PASSIVE - which means they don't require any user interaction. For example if you want an unattended or otherwise automated install. For an example of a passive install that DOES work correctly, I refer you to: msiexec /i mysql-connector-odbc-5.2.5-win32.msi" /passive This is how it should work. You see windows pop up with installation progress but NO interaction is required - it simply does a default install without asking the user anything or requiring any interaction. That's what a passive install is. And that's exactly what your community installer DOESN'T DO. I don't know how I can be more clear. To receive this response a year after reporting the bug is incredibly disappointing and frustrating. Are you even taking this seriously?
[27 Oct 2015 0:55]
Jose Gabriel Valencia Ornelas
Posted by developer: The current installer provide support for /QN or quiet where the user can specify CONSOLEARGS to specify what products and the configuration necessary if is required (for example for server) /PASSIVE is the equivalent to /QB!- that is similar to /QN but the UILevel changes from 2 to 3, will be analyzed to add the same support that we have currently with /QN to /QB!- so works in the same way, the current /QN support, the user MUST need to provide the CONSOLEARGS in order to the installer do an automatic installation(s) with the options and configurations provided.
[6 Nov 2015 21:22]
Jose Gabriel Valencia Ornelas
Posted by developer: /passive or /qb!- (is the same) work with a different UI Level that was not configured to be used by the installer, (only was weorking with /QN or /Quiet) in order to work with passive in the same way than /qn the UI Level validation was changed now it can be used like: msiexec /i mysql-installer-community-5.7.9.0.msi /passive CONSOLEARGS="install -type=Full -silent" or another one msiexec /i mysql-installer-community-5.7.9.0.msi /passive CONSOLEARGS="install server;5.6.25;x64:*:type=config;openfirewall=true;generallog=true;binlog=true;serverid=3306;enable_tcpip=true;port=3306;rootpasswd=root:type=user;username=user;password=password;role=DBManager -silent"
[10 Nov 2015 17:34]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Installer 1.4.12 release, and here's the changelog entry: A "passive" parameter was added to the Installer command-line. The "passive" option won't perform a complete install unless configuration options are used. For example, executing the following will not configure the MySQL server instance, nor will it create the MySQL service: msiexec /i mysql-installer-community-5.6.27.1.msi /passive CONSOLEARGS="install -type=Full -silent" Passing in configuration options to CONSOLEARGS is recommended, for example: msiexec /i mysql-installer-community-5.6.27.1.msi /passive CONSOLEARGS="install server;5.6.27;x64:*:type=config;openfirewall=true; generallog=true;binlog=true;serverid=1;enable_tcpip=true;port=3306; rootpasswd=secret:type=user;username=root;password=secret;role=DBManager -silent" Thank you for the bug report.