Bug #100501 Firewall Rule Port 33061 not set by MSI
Submitted: 12 Aug 2020 8:09 Modified: 12 May 2022 14:46
Reporter: Farzin Rezaeian Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL for Windows: Installer Severity:S3 (Non-critical)
Version:8.0.21 OS:Windows
Assigned to: CPU Architecture:Any
Tags: firewall, mysql installer, port 33061, Windows Server 2016

[12 Aug 2020 8:09] Farzin Rezaeian
Description:
Installed Mysql 8.0.21 using the MSI installer. Configuration for seed innodb Cluster was made.
The Installer only set Firewall Rule for port 33060 on local host Windows Server 2016.

Subsequently, other machines Mysql instances could not be added via dba.addInstance()
Cloneing through addInstance() parsed Connection errors to port 33061 on slave instances Mysql error log file.

Please update MSI... 

How to repeat:
Installed Mysql 8.0.21 using the MSI installer. Configuration for seed innodb Cluster was made.
The Installer only set Firewall Rule for port 33060 on local host Windows Server 2016.

Subsequently, other machines Mysql instances could not be added via dba.addInstance()
Cloneing through addInstance() parsed Connection errors to port 33061 on slave instances Mysql error log file.

Suggested fix:
Please update MSI... 
The Firewall Rule for port 33061  Inbound must be added by Installer.
[12 Aug 2020 13:03] MySQL Verification Team
Hi,
Normally I don't think our installer should touch the windows firewall at all as that's something user should do alone but if we are already doing it then we have to do it properly so I'll verify the bug.

all best
Bogdan
[12 May 2022 14:46] Javier TreviƱo
Support for production and sandbox InnoDB cluster server configuration types was removed in version 1.4.35. Not feasible to fix.