Bug #43900 Agent update installer forces mgmt hostname SSL port to 18443
Submitted: 26 Mar 2009 21:57 Modified: 7 Aug 2009 10:04
Reporter: Marcos Palacios Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: BitRock Merlin CPU Architecture:Any

[26 Mar 2009 21:57] Marcos Palacios
When updating an agent that uses SSL, to connect to the dashboard, on a port other than '18443', the resulting ini file will have the SSL port changed to '18443'. For example, if I had port '28443' then it changes it to '18443'.

If the agent does not use SSL, the port is kept the same: i.e., if I had '28080' then it does not change it.

How to repeat:
- install a 2.0 agent with the following parameter (in etc/mysql-monitor-agent.ini):
  agent-mgmt-hostname = https://<agent-id>:<agent-password>@
 This means: use the "28443" as the SSL port when installing the 2.0 agent and indicate/check "Use SSL".
- use the 2.1 agent update installer to upgrade the agent
- observe that the SSL port in the agent-mgmt-hostname parameter (in the new ini file) is now "18443".
[31 Mar 2009 11:44] BitRock Merlin
Should this issue be fixed for 2.0 and 2.1 versions? Please specify the "Target Version" tag, thanks.
[28 Apr 2009 19:00] Andy Bang
Please fix in both 2.0 and 2.1.
[29 Apr 2009 17:15] BitRock Merlin
Patch sent to Keith.
[4 May 2009 23:30] Keith Russell
Patch installed in versions =>
[5 May 2009 15:08] Marcos Palacios
Verified fixed in build - setting back to Patch pending for 2.0.6 build.
[31 Jul 2009 3:27] Enterprise Tools JIRA Robot
Keith Russell writes: 
Patch installed in versions =>
[4 Aug 2009 22:16] Enterprise Tools JIRA Robot
Marcos Palacios writes: 
Verified fixed in agent update installer build
[7 Aug 2009 10:04] Tony Bedford
An entry was added to both the 2.0.6 and 2.1.0 changelogs:

When updating an Agent from 2.0 to 2.1 the mysql-monitor-agent.ini was incorrectly updated.

This happened if the Agent was configured to use SSL to connect to the Enterprise Dashboard, on a port other than 18443. The update installer caused any value specified for the port to be changed to 18443. This did not happen if the Agent was not using SSL.